Bug #18442 for CGI-Session: CGI::Session::find call

Wed Mar 29 18:48:38 2006 Guest - Ticket created

Subject:

CGI::Session::find call

When calling find to enumerate all sessions stored, it will update the last modified timestamp. If you have a cron job that's running with an interval less than the expiration time, sessions will never expire. I would be useful to bypass updating the last modified timestamp for this call.

Thu Apr 13 21:41:21 2006 MARKSTOS [...] cpan.org - Severity Normal changed to Wishlist

Thu Apr 13 21:41:21 2006 MARKSTOS [...] cpan.org - Fixed in 4.12 added

Thu Apr 13 21:48:27 2006 MARKSTOS [...] cpan.org - Correspondence added

On Wed Mar 29 18:48:38 2006, guest wrote: Show quoted text

> When calling find to enumerate all sessions stored, it will update the > last modified timestamp. If you have a cron job that's running with an > interval less than the expiration time, sessions will never expire. I > would be useful to bypass updating the last modified timestamp for this > call.

Which driver are you referring to? Are you sure it's updating the modification time ("mtime") and not the last access time ("atime"). I've reviewed the "traverse" method of the various drivers and I don't see that this is happening explicitly. If you would like further work to happen on this issue, please submit a failing test in the style of "Test::More". See the test suite of CGI::Session for examples. You might also discuss the issue further on the CGI::Session users mailing list. Mark

Thu Apr 13 21:48:28 2006 The RT System itself - Status changed from 'new' to 'open'

Thu Apr 13 21:48:29 2006 MARKSTOS [...] cpan.org - Status changed from 'open' to 'stalled'

Thu Apr 13 23:13:47 2006 sherzodr [...] handalak.com - Correspondence added

Subject:	RE: [rt.cpan.org #18442] CGI::Session::find call
Date:	Thu, 13 Apr 2006 23:11:54 -0400
To:	<bug-CGI-Session [...] rt.cpan.org>, <"undisclosed-recipients:" [...] bestpractical.com>
From:	"Sherzod Ruzmetov" <sherzodr [...] handalak.com>

If it's a file driver, the OS should be updating the atime of the session file, but it has nothing to do with the way CGI::Session handles atime(). CGI::Session stores atime information inside the session data. This field is updated every time the session is loaded using CGI::Session->new(...) syntax. CGI::Session::find() doesn't call new(), it calls load(). But again, if you could create a small test script to re-generate the error, we'll look at it. Usually test scripts explain better than words :). -- Sherzod Show quoted text

> -----Original Message----- > From: via RT [mailto:bug-CGI-Session@rt.cpan.org] > Sent: Thursday, April 13, 2006 9:48 PM > To: undisclosed-recipients: > Subject: [rt.cpan.org #18442] CGI::Session::find call > > > > Queue: CGI-Session > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=18442 > > > On Wed Mar 29 18:48:38 2006, guest wrote:

> > When calling find to enumerate all sessions stored, it will

> update the

> > last modified timestamp. If you have a cron job that's

> running with an

> > interval less than the expiration time, sessions will never

> expire. I

> > would be useful to bypass updating the last modified timestamp for > > this call.

> > Which driver are you referring to? Are you sure it's updating > the modification time ("mtime") and not the last access time > ("atime"). > > I've reviewed the "traverse" method of the various drivers > and I don't see that this is happening explicitly. > > If you would like further work to happen on this issue, > please submit a failing test in the style of "Test::More". > See the test suite of CGI::Session for examples. > > You might also discuss the issue further on the CGI::Session > users mailing list. > > Mark > >

Thu Apr 13 23:13:48 2006 The RT System itself - Status changed from 'stalled' to 'open'

Sat Jun 10 20:07:16 2006 MARKSTOS [...] cpan.org - Taken

Sat Jun 10 20:08:42 2006 MARKSTOS [...] cpan.org - Status changed from 'open' to 'resolved'