On Tuesday 28 June 2005 11:47, Andrew Piskorski wrote: > On Tue, Jun 28, 2005 at 10:42:33AM -0700, Tom Jackson wrote: > > Here are some ideas using a file based storage: > > If you're already using an RDBMS anyway, why would you want to store > session info in files rather than the RDBMS? And if you don't have an > RDBMS, I would consider linking in SQLite rather than using plain > files. >
Actually if you want to know, I approached the data modeling from the Tcl side, since that is the language of AOLserver. Session data is barely structured, and mashing it into a RDBMS, which would be very generic, would actually remove the tiny bit of structure that exists. Basically you have variables, lists and arrays all tied togeather with a single key. Session data has a very specific and time limited purpose, it simply doesn't match up with an RDBMS, and I personally wanted to avoid an intermediate language/layer just to store data with a lifetime of 10 minutes, more or less. The concept here is that an application usually needs more data to run than ever gets loaded into the database. Tying your runtime behavior to a database becomes difficult to manage both locally and if you decide to copy the behavior to another server. So in my baby toolkit, I have avoided any database storage of configuration information, which makes it easy for me to copy services, develop applications more quickly, and solve the data model in Tcl first, because, in the end, everything goes through Tcl. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
