And I have seen that CGI::Session is not very fast, even when there are only a few sessions in a MySQL table, but... are there any other libraries that can do it better?
I have seen that CGI::session is made in such a way that anyone can write a driver for another databases or ways of storing data. I think that someone who knows better MySQL could re-write a CGI::Session::MySQL driver which will work better. Teddy ----- Original Message ----- From: "Perrin Harkins" <[EMAIL PROTECTED]> To: "William McKee" <[EMAIL PROTECTED]> Cc: <modperl@perl.apache.org> Sent: Monday, January 17, 2005 10:16 PM Subject: Re: CGI::Session or CGI::Application > On Mon, 2005-01-17 at 14:45 -0500, William McKee wrote: > > On Sat, Jan 15, 2005 at 08:15:31AM -0500, Michael Peters wrote: > > > CGI::Session does not appear to be well maintained. It's very popular > > > and I know many people who have tried to send in patches and fixes but > > > the author has been unresponsive. > > > > Which is really ashame since it's listed in the Phalanx 100[1]. > > Nonetheless, it's been working fine for me (via the > > CGI::Application::Plugin::Session module). > > Last time I looked at it, I was scared off by some of the things I saw > in the CGI::Session::MySQL module. It doesn't use the most efficient > SQL constructs (no cached statement handles, no bind_cols) and has a > locking mechanism that adds nothing (except overhead) over the standard > MySQL atomic operations. The PostgreSQL one doesn't use bind variables, > but rather manually quotes everything. It just didn't give me much > confidence in the module. > > - Perrin
