[
https://issues.apache.org/jira/browse/ORCHESTRA-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656569#action_12656569
]
Simon Kitching commented on ORCHESTRA-33:
-----------------------------------------
One other note: a ConversationContext object itself doesn't take up much
memory. Conversation objects within a context can use significant memory, but
they have a separate (and configurable) timeout.
> ConversationContext timeout should be configurable
> --------------------------------------------------
>
> Key: ORCHESTRA-33
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-33
> Project: MyFaces Orchestra
> Issue Type: Improvement
> Components: Conversation
> Affects Versions: 1.3
> Reporter: Simon Kitching
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
