How does your module differ from that of Apache::Session? If you didn't know, A:S does NOT depend on Apache or mod_perl. But it does do sessions very well, with all kinds of backing stores. How does your module handle locking? That can get tricky w/ file-based storage, but A:S has had it's methods tested by many users. Just a thought. If you're not too weded to your module, you might want to try Apache::Session. At a minimum, I'm sure you could take something useful out of it.
time passes...: From looking at your docs you probably didn't realize that A:S is usable in a CGI environment. Take a look. Apache::Session | [reply] |
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;
| [reply] |
As you said, it is redundant. But isn't it fun to build something from scratch, and better, to look back and see the lessons you've learned. Reinventing the wheel _can be_ fun, and sometimes it's even useful. I'd guess that it was some of both for you. :-)
| [reply] |
Cache::Cache does provide atomic updates. However, there's already a module out there for using Apache::Session with Cache::Cache, so this module is still probably redundant.
| [reply] |
