On May 26, 2005, at 5:48 PM, Titus Brown wrote:
> The short version is that the SessionManager included with Quixote
> is aimed at a single-process object-database backend like Durus,
> and it
> has been difficult for me to make it work nicely with other
> backends, or
> with threads.  YMMV, and I'd be interested to find out what my own
> blind
> spot(s) is/are...

I don't think I would call Durus a single-process backend.  Durus runs
client/server, but the majority of the Durus code runs in the
clients, and
there can be multiple clients.  The clients could even be in the same
process, if you really wanted it.