Please see the 8.5.4 Conversation context lifecycle of the specification.
@see ConversationScopedOptionally, a PersistenceContext can also be associated with a conversation.
There are various ways how to get access to a Conversation instance:
Conversation instances are typically created when an EL expression references a bean whose definition indicates that it is in a conversation scope.
A conversation instance is typically destroyed:
Conversation flow consists of a directed graph of {@link Prompt} objects.Each time a prompt gets input from the user, it must return the next prompt in the graph. Since each Prompt chooses the next Prompt, complex conversation trees can be implemented where the nature of the player's response directs the flow of the conversation.
Each conversation has a {@link ConversationPrefix} that prepends all outputfrom the conversation to the player. The ConversationPrefix can be used to display the plugin name or conversation status as the conversation evolves.
Each conversation has a timeout measured in the number of inactive seconds to wait before abandoning the conversation. If the inactivity timeout is reached, the conversation is abandoned and the user's incoming and outgoing chat is returned to normal.
You should not construct a conversation manually. Instead, use the {@link ConversationFactory} for access to all available options.
Conversation
object is used to set and interpret the semantics of the HTTP headers with regard to the encoding used for the response. This will ensure the the correct headers are used so that if chunked encoding or a connection close is needed that the headers are set accordingly. This allows both the server and client to agree on the best semantics to use.
@author Niall Gallagher
@see org.simpleframework.http.core.ResponseBuffer
@see org.simpleframework.http.core.Transfer
Note that the attributes associated with a conversation are not "conversation scope" as defined for a flow execution. They can be any attributes, possibly technical in nature, associated with the conversation. @author Keith Donald @author Erwin Vervaet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|