I'm preserving stateful session information server-side. I need to
periodically clean up, get rid of any persisted objects associated with
closed sessions. AFAIK tracking session closure is unreliable, so I thought
I'd just loop through the existing session id's to determine what could be
garbage collected.
Paul
> Doubt it. What do you need them for?
> -- Peter
[quoted text clipped - 4 lines]
>>
>> Paul
Doesn't compute. When a Session expires, everything in it is automatically
garbage -collected. Don't need to do anything.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
Short urls & more: http://ittyurl.net
> I'm preserving stateful session information server-side. I need to
> periodically clean up, get rid of any persisted objects associated with
[quoted text clipped - 12 lines]
> >>
> >> Paul
PJ6 - 22 Jun 2007 20:35 GMT
I agree, there may be exceptions thrown when my code attempts to access
disposed objects, but nonetheless, references to them that I keep in my own
static pool of information (using the SessionID as a key) remain until they
are removed.
Paul
> Doesn't compute. When a Session expires, everything in it is
> automatically
[quoted text clipped - 10 lines]
>>
>> Paul