Perrin Harkins writes: > Sorry if I came off overly critical. Many people have had problems > trying to use Mason with Apache::Session because of that article. This > is why on the Mason website the link to that article describes it as > outdated and steers people to newer documentation. (It probably should > also steer them to the new handler...)
I've deactivated the link and pointed to the new handler. > By using Apache::Session::Flex. The configuration for > MasonX::Request::WithApacheSession also lets you do this. I was planning to use Flex too. But I came upon an email from Jeff http://marc.theaimsgroup.com/?l=apache-modperl&m=100283817811419&w=2 saying "Regarding Flex, nobody uses it. It is for debugging. If you have a particular variant of Flex that you use all the time (very likely), you can code up a 6-line module to make a real implementation like all the other session modules. Flex is for debugging, period." Is this outdated information? Is Flex now considered reasonable for production? (Not sure why it "for debugging" in the first place.) Is there any disadvantage to using it versus creating a custom session class? > In my opinion, the locking approach taken in Apache::Session is not a good one for > the average web site and you should simply turn it off by using the NullLocker. Yes, we're about to add a note to MasonX::Request::WithApacheHandler indicating as much. I have heard so many complaints about MySQL locking, and have encountered problems with it myself, that I have to wonder why it is still in the package at all (much less the default)? Is there any real way to use it successfully? If I can get it to fail out of the box with my two development server processes and a few hits an hour, how could it ever be trusted in production? > The latest Apache::Session on CPAN is version 1.54, released in October 2001. Perhaps this answers my previous question. :) Jon -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
