On Thu, Mar 22, 2012 at 3:04 PM, Tim Allen wrote:
> So the only possible results are 0 and 3, because the 'synchronisation
> points' are at the edges of callbacks.
Ok, awesome. That's the bit that I couldn't quite understand. Thanks!
--
Uri
Please consider the environment before printing th
On Thu, Mar 22, 2012 at 2:18 PM, Ilja Livenson wrote:
> we have been stumbling on the same problems when using ZODB. The
> current solution is to defer db operations to a threadpool. We also
> have rdonly and rw transaction decorators, which can be used for
> speeding up processing/custom logic. I
On Thu, Mar 22, 2012 at 2:17 PM, Itamar Turner-Trauring
wrote:
> On 03/22/2012 08:05 AM, Uri Okrent wrote:
>> This implies that twisted can (and will) switch contexts from one
>> deferred to another even in the middle of execution of the first
>> deferred, correct?
>
Thanks for the excellent responses guys. So a couple more things...
On Thu, Mar 22, 2012 at 1:37 PM, Tim Allen wrote:
> A Deferred can wait on the result of other Deferreds; while one Deferred
> is waiting (say, waiting for a timer to go off, or waiting for network
> activity), others may be run
Hello all, I'm a twisted novice, but I was brought on to a project
where twisted is pretty heavily in use. I'm running into all sorts of
issues that make me wonder if we're using twisted properly or as it
was intended. I have been through the documentation, but I think I
need more in-depth answer
