I'm presented with a BUNCH of locking mechanisms when installing Apache::SessionX. I'd like to know a couple things that will be helpful!
1) What exactly are we locking with Apache::SessionX? As I understand it, sessions are handled via cookies so we are not actually locking anything but creating a unique ID for the cookies to hold and then we match that up with a session store on the server. 2) Which of the available methods for locking is best (most reliable vs. least processor intensive)? 3) Clearly, we can't use the Null lock here right? TIA, Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
