On Tue, 2004-02-24 at 11:42, Perrin Harkins wrote: > On Tue, 2004-02-24 at 10:44, Enrico Sorcinelli wrote: > > Wrapper or not, I think this is the moment to decide the future of > > Apache::Session. > > I'm not sure it needs to happen right this minute, but I do have an idea > of what I would like to see happen with sessions in the mod_perl world. > > Apache::Session has been a problem for a long time. Part of it is > Jeffrey's unresponsiveness to patches and bug reports, and part of it is > the design, with the tied interface, and the save-on-DESTROY, and the > mutually-exclusive locking. These have proved to be very problematic > for new users, and I think most people would be better served by a > simple OO interface with no magic.
By the way, I completely agree with all these problems. They are parts of the reason why I'm not really that interested in developing Apache::Session any more. The design has fundamental problems that are not show-stoppers but also are not that great. For example there is an unsolvable problem of exception-on-DESTROY, which would happen at arbitrary times, except Perl won't even raise an exception in DESTROY. This can lead to silent data loss. Also, although I think the locking mechanism is perfectly fine and suited for my purposes, a *lot* of people cannot understand how it works. -jwb -- 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
