Good point, except that the "sessions" in this case are not necessarily tied to "user sessions" - a new session id would be generated for each search, and embedded in the URLs to retrieve the data (I would never store these "session" ids as cookies). In fact this also allows people to share the search sessions, simply by exchanging the formatted URLs.

Would Cache::Cache offer any additional advantages with this scenario? The way I see it, CGI::Session will also generate the ids for me (and I can use the same mechanism for storing actual user sessions, should I need them).

(Incidentally, a few popular systems use this concept of "session" as different from an HTTP session - Lion's SRS comes to mind; so my users are quite used to the idea).

In reply to Re: Re: mod_perl and sessions by glwtta
in thread mod_perl and sessions by glwtta

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.