On Sun, 22 Feb 2004 22:38:20 -0600 (CST)
Dave Rolsky <[EMAIL PROTECTED]> wrote:

Hi Dave, 

> 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? 
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 :-)

Moreover it's very easy to integrate A::SM in many mod_perl app server (I use
and I've used A::SM with Mason for a long time before your
MasonX::Request::WithApacheSession release)

> I don't think this module really belongs in the Apache:: namespace, since
> it's not mod_perl specific.

Yes, Apache::Session namespace is a hystorical error... :-)
 
> 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.

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). 

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.
I've also started an experimental branch of Apache::Session in order to
customize (add) 'sessions' table fields.

After all, why not extend Apache::Session package simply by adding the wrapper
code instead of creating a new one?

by

        - Enrico



-- 
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

Reply via email to