Re: [orchestra] Conversation Timeouts (was changed scope configuration)

[simon <si...@chello.at>]

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 wondering where their beans went.

The http session really does have to be a sane default as otherwise
memory usage will eventually bring down the whole webapp. But with
Orchestra, the conversations do eventually go away - when the session
does.

My, we have spent a lot of bandwidth on a very small point :-)

It's nice to see people are interested in Orchestra though.

Regards,

Simon

On Sat, 2007-09-08 at 19:03 +0200, Bernhard Huemer wrote:
> 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
> the default behaviour of sessions is never to time
> out. If this element is not specified, the container
> must set its default timeout period.
> \\\
> 
> regards,
> Bernhard
> 
> On 08.09.2007 18:48, Mario Ivankovits wrote:
> > 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,
> > Mario
> >