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.<br>
<br><br> - Matt<br><br><div class="gmail_quote">On Tue, Oct 6, 2009 at 11:13 PM, Steve Steiner (listsin) <span dir="ltr"><<a href="mailto:listsin@integrateddevcorp.com" target="_blank">listsin@integrateddevcorp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><br>
On Oct 6, 2009, at 11:00 PM, Matt Perry wrote:<br>
<br>
> One thing of note is that you say you have concurrency issues<br>
> handled -- but with asynchronous I/O, there are no concurrency<br>
> issues, since there's no concurrency (at least, not at application<br>
> level). This is confusing at first but it's important to understand.<br>
<br>
</div>The concurrency to which I was referring was having multiple deferreds<br>
adding to the "getlist" semi-simultaneously.<br>
<br>
They have to obtain a lock on the "getlist" before they can add new<br>
things to "get", then they release it.<br>
<div><div></div><div><br>
Thanks,<br>
<br>
S<br>
<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com" target="_blank">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br>