Bas, fancy meeting you *here* ;-) I've recently nabbed the session management code from OpenACS and got this working on vanilla AOLserver. This uses nsv's to store stuff in memory and periodically writes back to the database. I can send you what I've got if you like.
Take a look at the OpenACS docs on their security design: http://openacs.org/doc/openacs-4/security-design.html Tim > -----Original Message----- > From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf > Of Bas Scheffers > Sent: Tuesday, February 18, 2003 9:59 AM > To: [EMAIL PROTECTED] > Subject: [AOLSERVER] nsv performance > > > Hi, > > I hope someone with a better understanding of the inner workings of nsv > can answer this for me: > > I would like to store application settings in the database, then on > startup, load these into memory and be able to update those on the fly > afterwards. nsv sets come into mind to do that. Would that be a good idea? > This will be mostly reading values, they would be rarely updated. Think > something in the order of 20 reads from different keys in the same set per > page. > > During a read, are sets locked for other readers, or only for writers? > > Could they also be used for storing session data? I was thinking one > "sessions" set, with session key as key and a tcl list-oflists as values. > In another set I would keep track of which sessions exist and should be > checked for expiration. This will mean there will be as many reads as > writes, "check out" the session at the beginning of a page, modify the > lists, check back into the set at the end of the page. Or is there a > better way to do sessions? > > Cheers, > Bas. >
