Hello,
As far as I can tell after browsing through the code, Turbine is not
using the timeout attribute in the TurbineUser class: I didn't find any
calls to user.get/setTimeout() or
getSession().setMaxInactiveInterval().
Is the session timeout management meant to be left to the application?
If so, shouldn't the place to store the timeout be also left to the
particular implementation, instead of assuming that it should be in
TurbineUser? Or did I miss something?
I guess that a possible approach could be to have a session.timeout
property, and place the following in the LoginUser action:
data.getSession().setMaxInactiveInterval(TurbineResources.getInt("sessio
n.timeout")
* 60);
Or Maybe in a SessionValidator subclass... Is there a favored approach?
Thanks,
Pere Torrodellas
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
