[Seaside] Seaside sessions

Ramon Leon ramon.leon at allresnet.com
Tue Sep 4 14:45:18 UTC 2007

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf 
> Of Sebastian Sastre
> Sent: Tuesday, September 04, 2007 6:22 AM
> To: 'Seaside - general discussion'
> Subject: [Seaside] Seaside sessions
> Hi there,
>     there is any kind of good practice to use session in production?
>     like an average duration that can be recomended?
>     I saw that in basecamp one can be logged and hours later 
> add some record and it reponds fine. Can that behavior be 
> implemented with seaside apps? if so, what approaches to 
> implement that one can use?
>     thanks,
> Sebastian 

I don't like web apps that timeout on me, nor do I like wasting server
resources with long session timeouts, so I keep the 10 minute timeout and
the root component of my apps create a single perodical that does nothing
that fires just short of the session timeout to touch the server every so
often.  This ensures any browser that is actually open won't timeout and any
actual unused sessions expires shortly.

Ramon Leon

More information about the Seaside mailing list