I replied in the first issue.
I'd be curious to see how other socket.io implementations deal with this issue.. since it is really due to statelessness being assumed by gunicorn and reverse proxies at many levels. In a stateless world, we don't really care if you hit the same server for your next request. Socket.IO deals with stateful connections.
Looking into the way people scale the nodejs version might be helpful.
Alexandre
--
You received this message because you are subscribed to the Google Groups "gevent-socketio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gevent-socket...@googlegroups.com.
To post to this group, send email to gevent-...@googlegroups.com.
Visit this group at http://groups.google.com/group/gevent-socketio.
For more options, visit https://groups.google.com/groups/opt_out.