[Seaside] Session termination
Derek Brans
brans at nerdonawire.com
Sun Aug 3 13:18:20 CEST 2003
Some methods of interest.
WARegistry>>collectExpiredHandlers
(handlersByKey reject: [:ea | ea isActive]) do: [:ea | self
unregisterRequestHandler: ea]
WASession>>isActive
^ Time totalSeconds - lastAccess < (self application preferenceAt:
#sessionExpirySeconds)
WARegistry>>unregisterRequestHandler: anObject
handlersByKey removeKey: (keysByHandler at: anObject).
keysByHandler removeKey: anObject
I suppose if you wanted to cheat you can add some termination code in
#isActive, in the case that it's not active.
I think the proper thing to do would be to add a call to some cleanup method
on WASession after the registry unregisters the session.
Derek Brans
Nerd on a Wire
Web design that's anything but square
http://www.nerdonawire.com
mailto: brans at nerdonawire.com
phone: 604.874.6463
toll-free: 1-877-NERD-ON-A-WIRE
----- Original Message -----
From: "Todd Blanchard" <tblanchard at mac.com>
To: "The Squeak Enterprise Aubergines Server - general discussion."
<seaside at lists.squeakfoundation.org>
Sent: Sunday, August 03, 2003 11:40 AM
Subject: [Seaside] Session termination
> How do WASessions get terminated?
>
> I'm asking because I want to release the database connection at some
> point once its expired (I'm just doing a naive one session one
> connection for now).
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside
>
>
More information about the Seaside
mailing list