[Cosmo-dev] Default timeout

[Matthew Eernisse]

As of my most recent checkin, the client-side timeout value is being set 
from the server-side value, so you'll only have to set it in one place.

Right now all these values are set in the dojoBoilerplate.jsp tag file, 
which is kind of hacky, but at least it's all in one place so it'll be 
easy to fix when we can do it the right way.

This also gives me a leg up on fixing bug 7646 -- client-side timeouts 
are still active even in ticket view.


Matthew


Jared Rhine wrote:
> Cosmo is distributed with a default session time of 30 minutes.
> 
> For the hosted service, I think the best user experience comes from a
> significantly higher number, probably 120 minutes.
> 
> I heard Matt suggest 60 minutes.  Seems like almost any default is fine, as
> long as there's a cosmo.properties or equivalent.  But I do encourage a
> pretty healthy timeout, if we're going to touch the default.
> 
> There's two places I know of where the value is set: web.xml session-timeout
> and pim.jsp TIMEOUT_MIN.  I actually patched them in one installation, but
> didn't test the results unfortunately.
> 
> I've seen reports that session.setMaxInactiveInterval(millsec) is a more
> reliable way to set timeouts for Tomcat-managed sessions.
> 
> -- Jared
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>