> On Thu, 2003-11-13 at 15:18, Jonathan Swartz wrote:
> > Interesting! I'll take a look. Have you seen any comparisons of features
> > anywhere?
>
> No, I don't think anyone has written up a comparison.
Well, at first glance it looks promising - lots of documentation and
examples, last release pretty recent - but then I took a look in
Apache::Session::MySQL and saw:
# stores the serialized data. Returns 1 for sucess, undef otherwise
sub store {
my ($self, $sid, $options, $data) = @_;
my $dbh = $self->MySQL_dbh($options);
my $lck_status = $dbh->selectrow_array(qq|SELECT GET_LOCK("$sid",
10)|);
unless ( $lck_status == 1 ) {
$self->error("Couldn't acquire lock on id '$sid'. Lock status:
$lck_status");
return undef;
}
...
return $dbh->selectrow_array(qq|SELECT RELEASE_LOCK("$sid")|);
}
So the default MySQL driver does locking just like Apache::Session, and
there's no built-in way to turn it locking. So it's possible that the same
locking problems that plague Apache::Session would happen in CGI::Session.
Argh!
Jon
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
