Comments for Eventlet

Comment on Powering Convore by Test, Demo

Test, Demo — Fri, 13 Jan 2012 03:30:39 +0000

$author you have great blog

Comment on Blocking Detection Article by investigazioni private

investigazioni private — Sun, 04 Dec 2011 15:05:01 +0000

Hey There Blog,
Very interesting, Powerful article marketing requires that you write a great title for your articles.
BTW great blogpost

Comment on Beautiful-er Eventlet by andre

andre — Mon, 21 Nov 2011 19:17:36 +0000

please, tell me, how i can install eventlet??!?!?!?
i try: easy_install eventlet, and dont work.
i make download of eventlet-0.9.15.tar.gz and can`t install, i do tar -zxvf ….. and can`t do make or make install.

please help me.

best regards
André

Comment on Safety! by Tony Morgan (@anthonymorgan)

Tony Morgan (@anthonymorgan) — Fri, 11 Nov 2011 18:35:44 +0000

The error message says, “If you do know what you’re doing and want to disable this error, call eventlet.debug.hub_multiple_reader_prevention(False)”, amusingly this contains a further check if you actually know what you’re doing, because you have to dig a little to discover it’s actually “eventlet.debug.hub_prevent_multiple_readers(False)” ;)

Comment on Scalable, WSGI-compatible Websockets by Ryan Williams

Ryan Williams — Wed, 12 Jan 2011 03:27:36 +0000

And when I say “a lot of middleware” I’m hedging my words because I haven’t tested all of them. There is a lot of non-spec-compliant middleware out there, and I wouldn’t want to speak for it.

Comment on Scalable, WSGI-compatible Websockets by Ryan Williams

Ryan Williams — Wed, 12 Jan 2011 03:26:03 +0000

Thanks for popping in, Graham.

This implementation works with a lot of WSGI middleware, that is what is meant by compatible. It definitely requires Eventlet.wsgi (or Spawning) as the web server, the point of the post is to spell that out. The technique is a possible direction for modifying WSGI to support websockets in the future.

Comment on Scalable, WSGI-compatible Websockets by Graham Dumpleton

Graham Dumpleton — Tue, 21 Dec 2010 22:31:24 +0000

If it requires ‘(a slight modification to) WSGI’ then it isn’t compatible with WSGI. Thus it is deceiving to say it it WSGI compatible.

Are you confusing a particular web servers implementation of a WSGI server with the WSGI specification itself. From all I have seen, it is not technically possible to run WebSocket protocol over a WSGI specification conforming implementation. That said, you might be able to hack some web servers that also support WSGI to support WebSocket at the same time, but that has nothing to do with the WSGI specification.

Comment on The Beauty of Eventlet by Justin Riley

Justin Riley — Wed, 24 Nov 2010 16:07:24 +0000

Nice post. I’ve been intrigued with nodejs but I certainly prefer Python over Javascript so it’s good to know about the eventlet library. Thanks for sharing.

Comment on Websocket Draft 76 by Ryan Williams

Ryan Williams — Thu, 05 Aug 2010 07:00:13 +0000

Ben, I apologize for my late reply. There is something seriously wrong with WordPress’s email notifications (or I am super-dumb). >:(

I absolutely support refactoring this code outside of the class. I kinda started to do that myself but didn’t finish. The handshake code you have there looks supa-clean.

Comment on Websocket Draft 76 by Ben

Ben — Tue, 15 Jun 2010 05:58:44 +0000

Hey Ryan,

This is great! Saves some work for me :-)

One request though: As I and probably a lot of other people will be using websockets in a web framework of some description, do you mind if I have a tinker with this and make it standalone outside of the WebSocketWSGI class?

What did you think of this code I showed you a couple of weeks ago as an API?
http://github.com/boothead/rpz.websocket/blob/master/rpz/websocket/handshake.py

Cheers,
Ben