Represents a running conversation.
TODO: we need a better way for a running user's conversation to expose information
to the caller.
The monitor of this object is used to notify the completion of a conversation.
Persisting Conversation
There are two different modes of 'persistence' for this object (and fibers.)
One is called hydration/dehydration, which is when we just persist the execution state
of fibers to the disk to save memory usage (and to improve fault tolerance.)
The other is called save/load, which is when we persist the conversation
object itself, but excluding the execution state of user code, to prepare
for the engine to go down.
author: Kohsuke Kawaguchi |