[Twisted-Python] Some suggestions

Itamar twisted at itamarst.org
Sat Aug 11 12:24:25 EDT 2001

Glyph Lefkowitz wrote:

>  * _That is okay_.  Don't start worrying too much about the performance
>   of Twisted's threading until you've got some significant benchmarking
>   problem; and when you discover that threading is slow, you can always
>   optimize by making it asynchronous instead :)  Chances are, however,
>   that your app can afford the speed hit if it's at all a typical server.
My main concern is *safety*. For example, I'm pretty sure making 
connectionLose() synchronized is not enough to make it thread safe. 
 Speed is good of course - and notice that synchronizing stuff slows 
down any non-threaded protocols I may be using along with my threaded one.

>  * There are some interesting ideas in this half/sync half/async pattern
>    that may be useful for your app, available at:
>	http://www.cs.wustl.edu/~schmidt/PDF/PLoP-95.pdf
I'll check it out.

More information about the Twisted-Python mailing list