eventlet VS Thespian Actor Library

index 714cb3a6..47c5c039 100644 --- a/tools/pip-requires +++ b/tools/pip-requires @@ -2,7 +2,7 @@ # NOTE: OpenStack avoids some versions of eventlet, because of the # following issue. # https://github.com/eventlet/eventlet/issues/401 -eventlet==0.31.1 +eventlet==0.33.3 msgpack>=0.4.0 # RPC library, BGP speaker(net_cntl) netaddr oslo.config>=2.5.0

root@agrover-OptiPlex-780:~# easy\_install -U eventlet Searching for eventlet Reading http://pypi.python.org/simple/eventlet/ Reading http://wiki.secondlife.com/wiki/Eventlet Reading http://eventlet.net Best match: eventlet 0.9.16 Processing eventlet-0.9.16-py2.7.egg eventlet 0.9.16 is already the active version in easy-install.pth Using /usr/local/lib/python2.7/dist-packages/eventlet-0.9.16-py2.7.egg Processing dependencies for eventlet Searching for greenlet>=0.3Reading http://pypi.python.org/simple/greenlet/Reading https://github.com/python-greenlet/greenletReading http://bitbucket.org/ambroff/greenletBest match: greenlet 0.3.4Downloading http://pypi.python.org/packages/source/g/greenlet/greenlet- 0.3.4.zip#md5=530a69acebbb0d66eb5abd83523d8272Processing greenlet-0.3.4.zipWriting /tmp/easy_install-_aeHYm/greenlet-0.3.4/setup.cfgRunning greenlet-0.3.4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-_aeHYm/greenlet-0.3.4/egg-dist-tmp-t9_gbWIn file included from greenlet.c:5:0:greenlet.h:8:20: fatal error: Python.h: No such file or directorycompilation terminated.error: Setup script exited with error: command 'gcc' failed with exit status 1` Why can't Python.h be found?

i would see if http://www.gevent.org/ or http://eventlet.net/ works on windows first

Nameko is built on top of the eventlet library, which provides concurrency via “greenthreads”.

"Even things that can't go wrong, do." - Troubleshooting Analog Circuits, Robert "Bob" Pease.

I had an application on a Raspberry PI that paired with a Bluetooth Low Energy device to fetch and send its data through a 3G dongle, on the premises of non-technical people who cannot troubleshoot, in different countries and time zones. There were a lot of things that could go wrong, and I wrote code to mitigate and recover, including pulling new code.

Part of it was using the Actor Model. I wrote actors to connect to the device, pulling data, sending data, computing what was sent, etc. The actor system handled the actors, when one died, it would recreate another one when an unhandled exception was met, for example.

https://en.wikipedia.org/wiki/Actor_model

If you're doing Scala, take a look at Akka. The new Scala has native support for this, if I remember correctly, without Akka.

If you're doing Python: https://github.com/kquick/Thespian, https://thespianpy.com/doc/