Geoff wrote:
>>My worry is that you'll end up with something like ZODB with ZEO if you want a SQL session store to be flexible enough to store any Python object that can be pickled (like the current SessionStores) but avoid concurrency problems. << I'm being very simple minded. I just pickle each dictionary entry and double-up all single quotes before sending it to PostgreSQL, and reverse the process on the way out. I don't use cacheing since PostgreSQL does this anyway, and because I need the session store to behave in a write-through manner for safety. >>If you don't need a fully general session storage, you can certainly roll your own specialized SQL session store for more limited types of data without too much trouble -- but it probably won't be as flexible as the one that comes with Webware, and it might be harder to use. (I'm speculating here.)<< This could be so, but I've not used either long enough to notice any limitations in my simplistic implementation. Basically, I can store anything that can be pickled, which is good enough for the moment. However, I doubt very much if it is as good as the Webware code... ...Edmund. _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
