Thanks for the clarifications on this.
If I were developing a new application that allowed users to hold onto tickets
for five minutes, I would have originally thought that I could simply use the
Conversation timeout. But since this is not the case, it would be important
that I understand
In order to get the correct behavior, I will assume that we need to make our
conversationTimeout to be equal to the session timeout.
This is good to know since it is the single biggest issue reported by the users
of our Seam based application.
View the original post :
Also, just to clarify, what is the foreground conversation?
Is it the conversation associated with the current request?
So the only conversations that would ever get cleaned up are those not part of
the current request.
Scenario:
I have two browser instances open and I leave my desk for
Right.
And this is very desirable behavior :-) Not at all unintuitive.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970427#3970427
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970427
This way idle conversations are timed out, yet the conversation that you're
currently in will last as long as your session lasts or until you finish the
conversation.
You don't want the foreground work you're currently doing to be ripped away
from you. But you do want a way for the resources
Right, exactly :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970433#3970433
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3970433
___
jboss-user mailing list
By the way, if anyone would find it useful, I can provide an alternative policy
that enforces a maximum number of conversations per user, instead of the simple
timeout.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3970434#3970434
Reply to the post :
