Re: Re: Re: Re: delete session using CGI::Session

Thanks for your code. After seeing more than a couple files build up in my /tmp/ directory I went back to the docs and realized something. The existing package is all about CGI and sessioning (well, duh) but has little for admin/debugging. The caveat you mention is rather spooky and can't be avoided with the existing API. It might be nice to have a 'peek' method that wouldn't affect anything to do with the 'state' of the session, such as time of last access. (Sure wish I had some of that "free time" people keep mentioning...)

Comment on Re: Re: Re: Re: delete session using CGI::Session

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: delete session using CGI::Session by LTjake (Prior) on Oct 08, 2003 at 19:46 UTC
Right, as soon as you load up a session, the ATIME is updated. The only other option would be to slurp up the contents of the session file, "thaw" it (with whatever you're using as a serializer), and manually check its expiration. Since we're dealing with an expiration interval of only 5 minutes, the ATIME modification isn't so much of a concern. However, as the expiration interval increases, the modification of the ATIME value becomes more troublesome. -- "To err is human, but to really foul things up you need a computer." --Paul Ehrlich	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: delete session using CGI::Session
by LTjake (Prior) on Oct 08, 2003 at 19:46 UTC

Right, as soon as you load up a session, the ATIME is updated.

The only other option would be to slurp up the contents of the session file, "thaw" it (with whatever you're using as a serializer), and manually check its expiration.

Since we're dealing with an expiration interval of only 5 minutes, the ATIME modification isn't so much of a concern. However, as the expiration interval increases, the modification of the ATIME value becomes more troublesome.

--
"To err is human, but to really foul things up you need a computer." --Paul Ehrlich

[reply]