[Seaside] Cleaning up (selectively) on logout
sebastian at flowingconcept.com
Thu Nov 15 22:41:20 UTC 2012
yeah, the question was not about security
On Nov 15, 2012, at 11:07 AM, Philippe Marschall wrote:
> On Thu, Nov 15, 2012 at 2:47 AM, Sebastian Sastre
> <sebastian at flowingconcept.com> wrote:
>> Any way to purge selectively the stuff that's cached in the image?
>> What do you need in addition to removing the session from the session
>> cache in the application?
>> yes, the session gets removed from the cache on #unregister: but what about
>> all the callbacks related to that session?
>> after session has been unregistered, would those stay in the cache for a
>> while? how long/short? in case they stay, is there any way to purge those
>> immediately on unregister?
> I haven't checked this with the code, so take it with a grain of salt.
> The callbacks should be registered in the continuation which should be
> registered in the session. So unregistering a session should make them
> all eligible for garbage collection. The callbacks should implicitly
> become invalid once the session is unregistered because the lookup
> first looks up the session. If the session can't be found you
> shouldn't be able find and therefore execute the callbacks.
> TL;DR everything should just work but you might want to check in the
> code yourself ;-)
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside