[Seaside] Seaside sessions

[Sebastian Sastre]

Hey that's clever. Simple and still quite secure (unless users abandon open
browsers in connected hosts). I think I'll try this,

	thanks Ramon,

Sebastian Sastre


> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Ramon Leon
> Enviado el: Martes, 04 de Septiembre de 2007 11:45
> Para: 'Seaside - general discussion'
> Asunto: RE: [Seaside] Seaside sessions
> 
> > -----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
> http://onsmalltalk.com
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside