On Thu, 2003-06-05 at 11:02, Perrin Harkins wrote: > On Thu, 2003-06-05 at 03:35, Dennis G. Allard wrote: > > (BTW, my more general goal is to have shared memory across multiple > > Apache threads as part of implementing sessions so that I can avoid > > doing a database write at every HTTP request just to save session IDs.) > > Hmmm, save session IDs? Why aren't you just putting those in a cookie > or in the URLs? > > If you meant to say session data rather than IDs, there are several good
Correct, I meant session data. > ways to do this, and IPC::ShareLite isn't one of them. It's too slow. > If this is for a single machine, try either IPC::MM or MLDBM::Sync. If > it's for a cluster, it's pretty hard to beat MySQL. > > - Perrin MySQL ShmySQL. A database that didn't have transactions until last year and still has no stored procedures Actually, I have nothing against MySQL. I happen to prefer Postgres, being a Berkeley kind of guy, Oracle due to its many strengths, and ap5 (http://ap5.com) for small applications since I prefer relational calculus and Lisp to relational algebra and SQL, the COBOL of the 21st Century. Flame off. I will politely decline a more detailed debate on these subjects, which are outside the scope of this mailing list. BTW, I wanted to use Apache::Session or CGI::Session but had some problems with each, possibly related to my newness with Apache 2/mod_perl 2/compat/whatever. So, I've decide to implement my own sessions for now, just for the hell of it, while I wait for Apache 2 dust to settle or land a project where I am forced to decipher the possibilities better. -- Dennis G. Allard <[EMAIL PROTECTED]> http://oceanpark.com
