Indeed, from technical perspective I think this is the only sane way forward. <br clear="all">--<br>Konrads Smelkovs<br>Applied IT sorcery.<br>
<br><br><div class="gmail_quote">On Mon, Jun 7, 2010 at 3:27 PM, Itamar Turner-Trauring <span dir="ltr"><<a href="mailto:itamar@itamarst.org">itamar@itamarst.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sun, 2010-06-06 at 23:07 -0400, Itamar Turner-Trauring wrote:<br>
<br>
> So, sounds like you want to define:<br>
> A) A way to hook up ZeroMQ event loop with Twisted event loop so that<br>
> both ZeroMQ and Twisted code can co-exist in same thread.<br>
<br>
</div>JP's proposal is superior to this... but may require changes to ZeroMQ.<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">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>