#18 startup argument - timeout

[Anonymous]

Originally created by: akarc... (code.google.com)@gmail.com

Now "timeout", the property for Daemon, is defined as
" session timeout in seconds or 0 to disable sessions."

I have found, actually the Session objects are still created, however, they are scheduled removed every second (Heart bit) in this case.

I wondering any live case for this is being used?
If yes, might 'constant' Session objects are created, the number of object is equal to threads(workers) number. and bypass remove action in heart bit loop. And at least session key should NOT sent to client in reply in this implementation.

How can i persist sessions?
unluckly, here ZERO is not defined for this purpose. :)

[Anonymous]

Originally posted by: marc.la... (code.google.com)@gmail.com

Hi, will look at this session problem. To persist sessions look at the sprout project; you have to set a cookie in the future (like one year for example) and then look at that cookie for a new session coming in here: Service.session(Session session, int type); where type is CREATE.

[Anonymous]

Originally posted by: akarc... (code.google.com)@gmail.com

works for me.

thanks, marc