Re: Apache::Session::MySQL, light/heavy proxy, wedging

[Todd Finney <suppressed>]

At 08:57 PM 1/30/2007 -0500, Perrin Harkins wrote:
> Before I spend too much time analyzing your symptoms, are you sure
> that your application requires excusive locks on sessions?  If not,
> you can use Apache::Session::Lock::Null for your locking class.

Eminently reasonable.

> The difference is that without exclusive locks
> you can get lost updates if a user tries to modify a session from two
> separate requests simultaneously.  (Not usually an issue, but it can
> be for certain kinds of applications.)

The sessions are modified on every request, to set a last_access time, and 
they're modified on login to set an authentication token.  I can't think of 
circumstances under which two different requests would attempt to modify a 
given session at the same time.

As much as I'd really like to understand what's actually happening here, 
I'll switch to A::S::Lock::Null if you think that's the best bet.  I don't 
see an example in the Apache::Session docs for switching the locking class, 
though - may I have a pointer?

thanks!