>2) The name change should happen.  However, there is already a
>Persistent:: set of classes, that is somewhat similar to 
>Apache::Session.  
>For example, it implements LDAP, MySQL, Oracle, Sybase, mSQL, and File
>storage.  These classes use all object calls
>e.g. $persistent->add_attribute().  So the chief difference seems to be
>the flexibility of the tied interface of Apache::Session (also mine is
>faster :)  So how does Persistent::TiedHash sound?
Hooray!

>3) The Apache::Session name whould be used for a module that actually
>manages the interaction between mod_perl and the browser.  The only
>problem I can see is that this module would have to start out at 2.0 or
>something, to avoid confusing CPAN.  ALternately, it could be called
>Apache::SessionManager instead.
It could also be called Apache::Persistant ?

Reply via email to