[ORCHESTRA-19] refactor conversationContext to allow nested conversationContext

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Conversation
• Assignee: Unassigned
• Reporter: Mario Ivankovits
• Created: 04/Apr/08 17:22
• Updated: 09/Oct/08 13:10
• Resolved: 09/Oct/08 13:10

Description

The conversationContext should be enhanced to allow nested conversationContext which is a requirement for dialog/flow implementations to separate the conversations for different flows.

The new conversationContext should be able to handle:

• a conversation context per windows
• multiple named conversationContexts
• a stack of conversationContexts to fulfill the requirement a dialog framework has with its subflows

Technically this might all be the same conversationContext implementation .... probably.