|No such thing as a small change|
Apache::Session::FIle Locking Mechanismby py_201 (Acolyte)
|on Sep 17, 2009 at 04:48 UTC||Need Help??|
py_201 has asked for the
wisdom of the Perl Monks concerning the following question:
I have implemented Apache::Session::File for session management in my web application. For that we specify Directory and Lock Directory while tieing the session and what i have observed is that for each session_id, it creates one file named after session_id in the directory and two files in LockDirectory, out of which one is named after session_id and other one has some random number in its name.what significance does these lock files have in session handling here?
Different requests to my web application(which can be concurrent also) alter session data in different ways. so sometimes session data gets lost in between those requests.
so my queries regarding sessions are:
What can i do to handle this data corruption? How Apache::Session::File handles concurrent access(for read,write) to session data.
Does Apache::Session::File provides some built in data locking mechanism. if yes, how does that work?Any help would be appreciated.