David Bolen wrote:
... nice clear explanation snipped ...
Basically the granularity of the sharing of the database thread (and
SA's connection to the database) is that of the callable you pass to
the database thread to execute. As long as you implement those
callables so they can run
Don Dwiggins d...@dondwiggins.net writes:
Hmmm, Could you elaborate a bit about the self-contained? I do have
some cases where I fire off a deferredList with several (independent)
queries in it. Might that be problematic?
My guess is that your independent comment is essentially the same
Don Dwiggins d...@dondwiggins.net writes:
Doing some exploration on the intersection of Twisted and SA, I came
across a message by David Bolen in February of 2007, describing a
simple database class that contained a background thread for
execution. I'd like to know if that work, or some
David, thanks for the quick reply.
Well, the server using it, in a slightly modified version from that
message, remains in production, and has been continuously since July
of 2007. So it's certainly worked for its intended purpose for me -
that is, offloading the SA database I/O to a
