[Twisted-Python] Lots and lots and lots and lots... of deferreds

Matt Perry matt at unshift.net
Tue Oct 6 23:23:44 EDT 2009

If everything is happening in a single thread, you probably don't need to
lock anything, because there's no shared access and therefore no race
conditions.  I have no idea how your app is written, so you may need them -
I don't know.  Just an observation.

 - Matt

On Tue, Oct 6, 2009 at 11:13 PM, Steve Steiner (listsin) <
listsin at integrateddevcorp.com> wrote:

> On Oct 6, 2009, at 11:00 PM, Matt Perry wrote:
> > One thing of note is that you say you have concurrency issues
> > handled -- but with asynchronous I/O, there are no concurrency
> > issues, since there's no concurrency (at least, not at application
> > level).  This is confusing at first but it's important to understand.
> The concurrency to which I was referring was having multiple deferreds
> adding to the "getlist" semi-simultaneously.
> They have to obtain a lock on the "getlist" before they can add new
> things to "get", then they release it.
> Thanks,
> S
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://twistedmatrix.com/pipermail/twisted-python/attachments/20091006/f5f14eab/attachment.htm 

More information about the Twisted-Python mailing list