Orbited seems as a nice solution. Haven’t tried it though. Update: things have changed in the last 2.5 years. We now have websockets in all major browsers, except IE (naturally) and a couple of very good abstractions over it, that provide many methods of emulating real-time communication. socket.io along with tornadio (socket.io 0.6) and tornadio2 … Read more
First of all, non-blocking I/O has nothing in common with green threads or coroutines, but it can affect how they’re scheduled. Now: Twisted is a classic non-blocking I/O framework — application code is written in async style using callbacks. Gevent and eventlet use the greenlet library for coroutines/greenthreads/greenlets. There is one dedicated greenlet for running … Read more
You might want to check out: Comparing gevent to eventlet Reports from users who moved from twisted or eventlet to gevent Eventlet and gevent are not really comparable to Stackless, because Stackless ships with a standard library that is not aware of tasklets. There are implementations of socket for Stackless but there isn’t anything as … Read more
It allows you to work with massive amounts of concurrency. Nobody sane would create one hundred thousand system threads, but you can do this using stackless. This article tests doing just that, creating one hundred thousand tasklets in both Python and Google Go (a new programming language): http://dalkescientific.com/writings/diary/archive/2009/11/15/100000_tasklets.html Surprisingly, even if Google Go is compiled … Read more
To make actors with gevent, use a Greenlet subclass with embedded gevent.queue.Queue instance used as an inbox. To read a message from the inbox, simply get() from the queue. To send a message to an actor, put it into that actor’s queue. Read about subclassing Greenlet here. If you need help with writing the Actor … Read more
There is lots of information about this available. For the “official word” on the issue, read the (closed) Python bugtracker issue. The core reasoning, by one of the people who made the decision, is detailed on this blog: Since a generator is essentially a souped-up function, we would need to save its bytecode, which is … Read more
In order of increasing complexity: Use the threading module Pros: It’s really easy to run any function (any callable in fact) in its own thread. Sharing data is if not easy (locks are never easy :), at least simple. Cons: As mentioned by Juergen Python threads cannot actually concurrently access state in the interpreter (there’s … Read more
I don’t know where that “Stackless is 10% faster” on the Wiki came from, but then again I’ve never tried to measure those performance numbers. I can’t think of what Stackless does to make a difference that big. Stackless is an amazing tool with several organizational/political problems. The first comes from history. Christian Tismer started … Read more