This makes more sense now, thanks :) For future ref, I found the following thread which gave an excellent explanation of Stackless vs Greenlet.
http://stackoverflow.com/questions/4263059/python-erlang-whats-the-difference-between-twisted-stackless-greenlet-event On Sat, Jun 23, 2012 at 9:00 PM, Richard Tew <[email protected]>wrote: > On Sun, Jun 24, 2012 at 7:20 AM, Cal Leeming [Simplicity Media Ltd] > <[email protected]> wrote: > > Could someone explain some of the difference between using Stackless, in > > comparison with using Eventlet? > > > > After using Stackless for almost 7 years and having to deal with some > insane > > bugs (such as hanging on network stack under high load scenarios), I > almost > > immediately fell in love with Eventlet for its simplicity and performance > > for our high network I/O applications. > > > > However, I don't understand the fundamentals of libevent or stackless > enough > > to know how to compare them. > > > > Any input would be much appreciated, even if it's just a poke in the > right > > direction on Google ;) > > Stackless is a green threading/microthreading solution. Greenlet is a > similar solution. Libraries like eventlet are built on top of > Stackless or greenlet, and make use of what they provide. You could > as equally well have a working libevent solution built on top of > Stackless, as on top of greenlet. Your problems were due to whatever > networking solution you chose to use. > > Hope this helps, > Richard. > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless >
_______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
