jmoiron plays the blues

created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
created gaspar, generic eventlet+zmq worker library
5789d354 to gaspar change the socket shutdown sequence to catch "Not connected error", which we don't care about, and fix the test suite on osx where eventlet does not build an epoll hub
f60ecfd7 to gaspar fix a weird issue where closed zmq sockets with linger set to 0 never get evicted from the eventlet hub; since this bug is not important to us and only shows up in unit testing, reset the hub after each test
6ed7097d to gaspar fix gaspartests (nosetests -s works now) on vanilla eventlet of latest revision; the duplicate fds were related to sockets that had been closed but not yet shutdown; calling socket.shutdown() beforehand eliminates these problems
756dc804 to gaspar adding a test that verifies zmq deals with big messages (the bug i was looking for ended up being in my own socket handling code)
created gaspar, generic eventlet+zmq worker library
5789d354 to gaspar change the socket shutdown sequence to catch "Not connected error", which we don't care about, and fix the test suite on osx where eventlet does not build an epoll hub
f60ecfd7 to gaspar fix a weird issue where closed zmq sockets with linger set to 0 never get evicted from the eventlet hub; since this bug is not important to us and only shows up in unit testing, reset the hub after each test
6ed7097d to gaspar fix gaspartests (nosetests -s works now) on vanilla eventlet of latest revision; the duplicate fds were related to sockets that had been closed but not yet shutdown; calling socket.shutdown() beforehand eliminates these problems
756dc804 to gaspar adding a test that verifies zmq deals with big messages (the bug i was looking for ended up being in my own socket handling code)
4d675283 to gaspar use makefile and read(n) instead of recv(n) in gaspar server, which prevents us from reading less than the desired buffersize and truncating messages