in reply to Re: Problems getting session management to work: is_expired seems to lie to me
in thread Problems getting session management to work: is_expired seems to lie to me

Thanks, good catch. Alas, adding that to the end of my script changed nothing.

Out of curiousity, is you do not use CGI::Session, what do you use for session management?

Thanks

Ted

  • Comment on Re^2: Problems getting session management to work: is_expired seems to lie to me

Replies are listed 'Best First'.
Re^3: Problems getting session management to work: is_expired seems to lie to me
by Corion (Patriarch) on May 06, 2013 at 21:40 UTC

    Currently I use Dancer with Dancer::Session.

    Also, your script is still very long and includes lots of unrelated stuff, like that try/catch stuff and HTML generation. I recommend ripping all that out to make the structure more obvious.

[reply]

      Thanks

      I may take a look at Dancer later, if time permits.

      You call 30 lines of code long? I am used to real world applications that, taken together, involved as much as half a million lines of code. I guess that is a matter of perspective. In any event, the try/catch stuff can be easily deleted, but that leaves only an anchor to reinvoke the CGI script on the first access to it. Without some content on the page, you have no way to know, without accessing the server logs, whether or not the script worked. Further, the HTML generation is an essential part of using CGI to generate pages, and as I pointed out to the other fellow, I encountered problems with is_expired only in the context of the code actually running in a CGI script.

      Thanks

      Ted

[reply]
        When looking for a problem, I call 30 lines long. You seem to enjoy searching for your problems in long code. I prefer to find my problems in short code, because usually after removing all unnecessary parts all that remains is the problematic code.
[reply]

In Section Seekers of Perl Wisdom