On Jul 29, 2011, at 4:38 AM, Erik Allik wrote:
> Thanks for another clear answer! I'll simply ignore zc.twist (for now
> at least) and set up a classic thread pool.
> I'll still probably use zc.twist's source as an example of how to
> write transaction retrial on ConflicErrors and ClientDisconnec
Thanks for another clear answer! I'll simply ignore zc.twist (for now
at least) and set up a classic thread pool.
I'll still probably use zc.twist's source as an example of how to
write transaction retrial on ConflicErrors and ClientDisconnecteds as
I haven't found anything similar elsewhere.
Erik
On Jul 28, 2011, at 6:38 PM, Erik Allik wrote:
> Gary, since you're the author of zc.twist (as I understand), I take
> this as an exhaustive answer, and thank you :)
>
> However, I'm still curious to know zc.twist would provide any benefit
> when used together with a thread pool.
> The thread ex
Gary, since you're the author of zc.twist (as I understand), I take
this as an exhaustive answer, and thank you :)
However, I'm still curious to know zc.twist would provide any benefit
when used together with a thread pool.
The thread examples in its README (which I find hard to understand)
indica
Hello Erik. As the author, I'll suggest that you move on to a ZODB connection
pool used by the usual Twisted-provided thread pool. zc.twist is maybe
interesting and maybe clever, but of very limited usefulness. I suspect it is
only used in zc.async, and that's probably as it should be. It's
