Andrew Bennetts wrote:
If you meant “can handle many concurrent connections” instead, I'd suggest Twisted, it tends to excel at that sort of task (and without threads, usually). Personally, even if threads are required I'd probably lean towards using it anyway :)
Threads are not a hard requirement, and Twisted would certainly be interesting to learn, but there are a few cons against it:
- first of all, event-driven programming is still a bit exotic and many more people are familiar with threads; and the code I'm writing will probably be in use for a long time and not just me will work on it. I can't realistically expect them to learn Twisted just to deal with my stuff (even being allowed to use Python was a bit of a challenge, my environment is almost all Java).
- in the long run, the threads support in core Python is much more certain to be there in at least a few years time, but future of Twisted, however good it is, is not so certain.
Joys of corporate pressures and conformity for you. -- Regards, mk -- Premature optimization is the root of all fun. _______________________________________________ paramiko mailing list paramiko@lag.net http://www.lag.net/cgi-bin/mailman/listinfo/paramiko
