Just to jump in here.. A few weeks ago I was looking for a session manager like the one you are describing. The key feature that I cannot find in any session manager is to use cookies if they exist, else fall back to using the query string. This is pretty much mandatory for ecommerce sites. I was looking through the source for apache::sessionmanager and it looked like you could use one or the other, but not both at the same time. So I ended up using apache::session and writing my own wrapper around it to do this.
I also agree on someone keeping apache::session up to date, even if it's just to keep the versions current so they show a current date. I was reluctant to use apache::session because it looked out of date, until I dug around and found out that it's still one of the best all around session managers for apache (I avoid using CGI::anything if I can help it). Chris ----- Original Message ----- From: "Dave Rolsky" <[EMAIL PROTECTED]> To: "Enrico Sorcinelli" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 24, 2004 8:28 AM Subject: Re: [OT-ish] Good name for generic wrapper around Apache::Session? > On Tue, 24 Feb 2004, Enrico Sorcinelli wrote: > > > > Yes, I know about Apache::SessionManager but unfortunately it is tightly > > > tied into mod_perl, going so far as to subclass the Apache class (which I > > > think is a bad idea, in this case). > > > > Unfortunately why? > > Because I want something that works outside of mod_perl as well ;) It's > unfortunate because rather than using your code, I have to write my own. > > > Apache::SessionManager allows session transparent URI tracking and it creates a > > session object and makes it available to all other handlers (sessions can be > > useful in authentication/authorization phase) so I've tied A::SM with mod_perl > > because I don't know any Perl related technologies (other than mod_perl itself) > > that allows this :-) > > Tying it to mod_perl is fine. Subclassing it makes no sense, and would > make it impossible to use with Apache::Filter, for example. > > > > Ideas are very, very welcome. > > > > In my working (and not yet released) A::SM version, I've had the same idea by > > adding a beta class wrapper to Apache::Session inside the package. > > > > So an idea could be: why reinventing the wheel? :-) I agree with a unique > > Apache::Session wrapper used by Apache::SessionManager or MasonX or ... > > > > BTW, I could plan to use this wrapper even for my Apache::Template and > > CGI::Application (A::SM-based) plugins. > > Well, my wrapper is pretty much done, and I need it now ;) However, if > you release yours later and it does the same stuff, I'd be happy to > replace mine with yours. > > > Wrapper or not, I think this is the moment to decide the future of > > Apache::Session. Recently, I've read many messages in this list where people > > says: "Apache::Session is 'out of date'" so users use CGI::Session. But > > Apache:Session is still a valid framework(!): it needs only a better (that is > > continous) maintenance (for example if Jeffrey Baker cannot, I can spend a bit > > of time for this). > > Doh! Better darn you flame retardant underwear. I volunteered to > maintain Apache::Session way back in 2001, before Jeffrey release 1.54, > after leaving a broken 1.53 on CPAN (Flex was broken) for a _long_ time, > and boy did he flame me. Never suggest that Jeffrey is anything less than > a sterling pillar of the community, responsive to bug reports, and an > all-around swell guy ;) > > > In the past I've made a patch to Apache::Session and I've mailed it (cc > > also to this list) to the author without response. Moreover I've seen other > > unapplied patches. > > No, tha'ts inconceivable! > > > After all, why not extend Apache::Session package simply by adding the wrapper > > code instead of creating a new one? > > Well, I don't think the wrapper needs to be distributed with > Apache::Session. > > > -dave > > /*======================= > House Absolute Consulting > www.houseabsolute.com > =======================*/ > > -- > Report problems: http://perl.apache.org/bugs/ > Mail list info: http://perl.apache.org/maillist/modperl.html > List etiquette: http://perl.apache.org/maillist/email-etiquette.html > > -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
