[ORCHESTRA-33] ConversationContext timeout should be configurable

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3
• Fix Version/s: 1.3.1
• Component/s: Conversation
• Assignee: Unassigned
• Reporter: Simon Kitching
• Created: 15/Dec/08 08:00
• Updated: 22/Feb/09 12:55
• Resolved: 22/Feb/09 12:55

Description

The ConversationContext class has a timeout property, so that all data in the context will be discarded if the context is not used for the timeout period.

The default value is 30 minutes. However there is no obvious way to configure this timeout:

• nothing in Orchestra ever calls ConversationContext.setTimeout
• the ConversationManager cannot be overridden, as ConversationManager.getInstance calls "new ConversationManager" directly.

Note that setting the ConversationContext timeout is not particularly important; because it is in the http-session, it is deleted when the session is deleted. However if a user has multiple windows open on an app, and then closes a window the ConversationContext continues to exist until the timeout occurs; some people may therefore wish to control how long that timeout is.