Hi!
IMHO, a conversation should behave exactly the same as the session
does today - per default. There is nothing elementary different just
because you can have a multitude of conversations per user.
Getting in touch to the servlet timeout means we have to extend the
FrameworkAdapter
[EMAIL PROTECTED]
Date: Saturday, Sep 8, 2007 8:36 pm
Subject: Re: [orchestra] Conversation Timeouts (was changed scope
configuration)
To: Reply-MyFaces Development dev@myfaces.apache.orgTo: MyFaces
Development dev@myfaces.apache.org
Ok, so I guess orchestra could use that same
Currently the config for a scope (from which a conversation inherits its
properties) looks like this:
bean class=...orchestra.spring.SpringConversationScope
property name=timeout value=30/
/bean
If no timeout property is present, then no timeout applies.
Otherwise, the specified
Hi!
If no timeout property is present, then no timeout applies.
Otherwise, the specified timeout applies.
You are right too with all you said.
Hmmm No pc here yet, but, how do a servlet container behave if there is no
session timeout configured or is it a required configuration?
Ciao,
Hello,
according to the Servlet specification:
///
The session-timeout element defines the default
session timeout interval for all sessions created
in this web application. The specified timeout
must be expressed in a whole number of minutes.
If the timeout is 0 or less, the container ensures
Ok, so I guess orchestra could use that same convention. This is still a
magic number that people will need to look up in the docs, though.
I still think it is more intuitive for people to not get a conversation
timeout unless they configure one. There will be absolutely no surprised
developers
-
From: simon [EMAIL PROTECTED]
Date: Saturday, Sep 8, 2007 8:36 pm
Subject: Re: [orchestra] Conversation Timeouts (was changed scope
configuration)
To: Reply-MyFaces Development dev@myfaces.apache.orgTo: MyFaces
Development dev@myfaces.apache.org
Ok, so I guess orchestra could use
Hi!
Currently orchestra has a feature that causes conversations that have
not been accessed within 30 minutes to automatically be deleted.
Similarly, conversation-contexts that have not been accessed within 30
minutes also get deleted.
This came up [1] in relation to Shale dialogs [2],
Forwarded Message
From: simon [EMAIL PROTECTED]
To: MyFaces Development dev@myfaces.apache.org
Subject: Re: [orchestra] conversation timeouts
Date: Sat, 18 Aug 2007 13:07:29 +0200
On Sat, 2007-08-18 at 12:47 +0200, Mario Ivankovits wrote:
I briefly
considered having an app
Forwarded Message
From: simon [EMAIL PROTECTED]
To: MyFaces Development dev@myfaces.apache.org
Subject: Re: [orchestra] conversation timeouts
Date: Sat, 18 Aug 2007 13:35:07 +0200
On Sat, 2007-08-18 at 10:19 +0200, simon wrote:
The current implementation is for a Thread
Forwarded Message
From: simon [EMAIL PROTECTED]
To: MyFaces Development dev@myfaces.apache.org
Subject: Re: [orchestra] conversation timeouts
Date: Sat, 18 Aug 2007 18:44:19 +0200
Hi Adam,
Thanks for your comments.
Yes, hitchhiking on other requests would be great - if we
Hi!
One issue is that garbage collection only happens at some random time
after the session is no longer used. So the timeout thread could end up
calling into the ConversationManager even after the session has been
explicitly removed. Possibly the ConversationManager could implement
Hi All,
Currently orchestra has a feature that causes conversations that have
not been accessed within 30 minutes to automatically be deleted.
Similarly, conversation-contexts that have not been accessed within 30
minutes also get deleted.
I don't personally see the use of this, but have been
Hi!
Currently orchestra has a feature that causes conversations that have
not been accessed within 30 minutes to automatically be deleted.
Similarly, conversation-contexts that have not been accessed within 30
minutes also get deleted.
I don't personally see the use of this, but have been
Mostly ignorant of orchestra, but:
Could you hitchhike on other requests? On any request,
look through a conversation list, and any that haven't
been accessed within 30 minutes get deleted.
If no requests are coming in, then one really doesn't
care about excessive resource use. :)
Finding a way
On 8/18/07, simon [EMAIL PROTECTED] wrote:
Hi All,
Currently orchestra has a feature that causes conversations that have
not been accessed within 30 minutes to automatically be deleted.
Similarly, conversation-contexts that have not been accessed within 30
minutes also get deleted.
I don't
16 matches
Mail list logo
