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
