No you should be fine.
Seaside only stores about 20 back button clicks.
The only problem you might have is if you get a huge number of
sessions but in your application that may not be a problem.
Just as a note. The session time out only applies to sessions that
have had no activity for that period of time. So I don't think you
would need an 8 hour timeout. A 30 minute or 1 hour timeout might be
better.
Will
On 21-Feb-06, at 7:42 AM, Martin J. Laubach wrote:
> I'm thinking about doing a helpdesk support application using
> seaside -- with that in mind, this means that the usual session
> will last for about 8 hours, and needs a session timeout in that
> range as to minimize the need to login (ie. they login in the morning
> and then use the same session all over the day). Is that something
> one needs to be concerned about?
>
> Will it accumulate a lot of cruft in memory just to support the
> back button? As the helpdesk people won't usually use the back
> button, is there a possibility to jettison older state information
> (say older than 15min -- as opposed to the 8h session timeout), and
> if they really go back there, will be redirected to some kind of main
> menu page?
>
> As said, I'm not sure that is really relevant -- is it?
>
> Regards,
>
> mjl
> _______________________________________________
> Seaside mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
