[Seaside] Seaside sessions

Boris Popov boris at deepcovelabs.com
Tue Sep 4 14:08:31 UTC 2007

I would say typical length of your session depends on the pattern of use
combined with security considerations. Former is very easy to determine
if you use Google Analytics (see "Avg. Time on Site") or similar web
metrics product. Say, if users typically spend ~5 minutes on your site
anyway, a timeout of 10 minutes should not be disruptive to anyone.
Latter is an arbitrary value that you are comfortable with (or have
regulations to comply with), for instance web banking applications try
to keep it to a minimum to minimize risks associated with users leaving
their browsers open.


DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----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
> apps? if so, what approaches to implement that one can use?
>     thanks,
> Sebastian

More information about the Seaside mailing list