[Twisted-web] Having reactor run at the main thread make things harder for late adopters

Tzury Bar Yochay tzury.by at gmail.com
Tue Nov 4 17:04:55 EST 2008

> This kind of thread work is what Twisted can do for you.  Either do it
> with threads or with Twisted.  Queue may be more than you need to handle
> the client-client connections.
> Referring to the FAQ Glyph recommended to you,
> http://twistedmatrix.com/trac/wiki/FrequentlyAskedQuestions#HowdoImakeinputononeconnectionresultinoutputonanother
> Instead of broadcasting to a list of connections set up a method to
> obtain the single appropriate connection and write to that.

Thinking about this over again I decided to bring my application to
Twisted. I will give up the pending queues and will make the code more
readable and control-flow much more traceable.

Thanks very much for your advice and sorry for the reply. (i simply
pressed `r` in my gmail and started typing...)


More information about the Twisted-web mailing list