comment on

Thanks for your reply. I wasn't sure if Apache::Session worked outside Apache or mod_perl. Thankyou for clearing that up.

Looking again at the docs for Apache::Session, the thing that seems to be missing there is timing-out the session. Admitedly, it would be easy to do this yourself in your application - adding a timestamp or something to the session. But I need to look more closely at it to see if this is the case.

Given that Apache::Session is not dependent upon Apache and the existance of Apache::Session::CacheAny, I think perrin is right - this module is redundant, and I shan't be uploading it to the CPAN. But, it was a worthwhile exercise and it will be available on my website if anyone is interested.

Cheers, Simon

___ Simon Flack ($code or die)
$,=reverse'"ro_';s,$,\$,;s,$,lc ref sub{},e;$, =~y'_"' ';eval"die";print $_,lc substr$@,0,3;

In reply to Re: Re: ANNOUNCE: CGI::Session::Simple by $code or die
in thread ANNOUNCE: CGI::Session::Simple by $code or die

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks