Tim, Have you released your findings, or considered doing so? Writing down what you found to be good and bad about each approach, as well as making your final solution available, would probably be helpful to others that may find themselves in that situation.
Rob Seeger Tim Moss wrote on 2/8/2005, 5:01 PM: > An example: > > - When I started using AOLserver I wanted to have user sessions so I > looked > around at what there is. > AOLserver itself offers nothing, so I looked around for modules > > - there's several, some that use files for storing sessions, some that > use > the database, some that are in server memory. Some are pure Tcl, some > are > pure C modules (and not so portable), others are hybrids. > > So which one should I use? > > There's no information about how or if any of them are actually being > used, > by how many users, how they compare performance wise etc. etc. > > So I tried them out - some I couldn't get to work, some wouldn't compile, > some wouldn't scale etc. so my question was left unanswered. > > The solution: > > Rip the session code out of OpenACS. It worked, it was tried and tested > (though not in the 'ripped' form), it scaled to multiple servers, it was > pure Tcl and so very portable, it was heavily designed for performance. > > > However, this took a load of time to reach this point and it would > have been > nice if there was a module providing all of this the came with the core > AOLserver. > Sure it wouldn't meet everyone's needs but it would be a good starting > point > and if its pros and cons were documented then a developer could weigh > up the > benefits of using it against writing their own to meet specific > requirements. > -- 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.
