That’s an interesting point you bring up about scalability. Eventlet also uses optimized event libraries (libevent), so it’s probably a tie there. The biggest problem, as I understand it, is that CPython is actually slower than V8, per this shootout link: http://shootout.alioth.debian.org/u64/benchmark.php?test=all&lang=v8&lang2=python That’s lame, and it basically means that *any* Python-based library is going to be slower than a V8-based one, just right off the bat. Haven’t tried any benchmarking of this particular application myself.

As to readability, yes, not fiddling with sockets is nice (and there are some conveniences to get around this to some degree that I didn’t use), but for me the biggest question is whether to have callback functions or not; a while loop makes the control flow a lot clearer to my eye. This becomes more of a factor with applications that are more complex than this simple example. But, I definitely agree that it’s subjective; some people really like thinking in terms of piles of callbacks, some people don’t!

Your eventlet example does look good. Regarding being more readable than node.js solution, I would say that’s highly subjective. I still find the node.js example more readable because that shields me from low level socket fiddling.

I am not too sure about being as scalable as node.js. node.js runs on V8, uses optimized event libraries and runs code close to the iron compared to python’s bytecodes. There are a couple of benchmarks where node.js has out-performed Twisted and Tornado. Unfortunately, I couldn’t find the links. I would try to benchmark my solution and yours. Let me know if you have done any benchmarking.

PS: I fixed the python solution links.