Apache::Session Locking

[tarkhil]

 "Kimbro" == Kimbro Staken writes:

Kimbro I'm trying to setup Apache::Session under Embperl with a MySQL
Kimbro datastore. I have multiple machines that will be serving the site thus
Kimbro all machines will access the datastore. In the documentation it says to
Kimbro use the DBIStore with a DaemonLocker which is fine. However there seems
Kimbro to be no documentation on how to use the DeamonLocker. I see it is
Well, I've ended up using NullLocker. I still don't understand how
Apache::Session could work. Any lock-releasing is done ONLY in DESTROY 
method, and while it should perform excellently in CGIs, I wonder how
locks ever gets released in mod_perl environment...

-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145][[EMAIL PROTECTED]]

Apache::Session Locking

[Kimbro Staken]

I'm trying to setup Apache::Session under Embperl with a MySQL
datastore. I have multiple machines that will be serving the site thus
all machines will access the datastore. In the documentation it says to
use the DBIStore with a DaemonLocker which is fine. However there seems
to be no documentation on how to use the DeamonLocker. I see it is
opening a port to connect to a process but no where do I see what the
process it connects to should be. Does anyone know what the process is
that it needs to connect to? Is locking even necessary when using MySQL
since MySQL provides its own syncronization?

Thanks

-- 
Kimbro Staken
Chief Technology Officer
Infostreet Inc.