Comments on: A minimal Python WebSocket server

By: Liam

Liam — Sat, 07 Jan 2012 14:08:00 +0000

Is there any chance you can update this article, I can’t seem to get it working so I assume this is an old protocol. Been searching for months just for a really simple implementation fo WebSockets

By: David Notaker112358

David Notaker112358 — Sat, 31 Dec 2011 15:51:00 +0000

Nice. One minor issue though: on some versions of python, the following section of code results in an EOL:

handshake = ’ HTTP/1.1 101 Web Socket Protocol Handshakern Upgrade: WebSocketrn Connection: Upgradern WebSocket-Origin: http://localhost:8888rn WebSocket-Location: ws://localhost:9999/rnrn ’

The problem can be fixed by using triple quotes instead of end-of-line backslashes:

handshake = ”’
HTTP/1.1 101 Web Socket Protocol Handshakern
Upgrade: WebSocketrn
Connection: Upgradern
WebSocket-Origin: http://localhost:8888rn
WebSocket-Location: ws://localhost:9999/rnrn
”’

By: James Mills / prologic

James Mills / prologic — Fri, 25 Feb 2011 02:21:00 +0000

Based on the code found in this blog (and other reading material on the web) circuits.web (1) as of revision fe3965b21fe2 now implements a working WebSockets Server:

https://bitbucket.org/prologic/circuits/changeset/fe3965b21fe2

This allows you to have a WebSockets server that sits alongside your application server (no need for a separate server, etc). This will be integrated into the circuits.web namespace before the next release.

cheers
James

1. http://bitbucket.org/prologic/circuits/

By: Johan Brissmyr

Johan Brissmyr — Thu, 03 Feb 2011 09:08:00 +0000

Yes, you’re right. The drafts are not yet stable. I’ll update the post and state the relevant draft version.

By: Roger Erens

Roger Erens — Tue, 01 Feb 2011 13:48:08 +0000

You might make note that this code is a little outdated now that draft-74 has been superseded. Problem (at least for me) is to find out which browser-version is using which draft…

Thanks for your example, though.

By: MrGretchev

MrGretchev — Sat, 19 Jun 2010 01:39:23 +0000

Thank you so much. I’ve been playing with a few other examples, but as has been said before, have too much functionality for a simple demo. I just wanted to handshake and send data, which is what you do here!

Thanks again!

By: Ben

Ben — Sat, 29 May 2010 05:43:48 +0000

Hi Eventlet now has support for websocket in core:

http://eventlet.net/doc/examples.html#websocket-server-example

And I’m currently adding suport for it to repoze.bfg in the rpz.websocket library:

http://github.com/boothead/rpz.websocket

The big advantage of eventlet is that the socket fiddling has already been taken car of to be non blocking, and the big advantage of repoze is that you can have a websocket connections available at the same url as the original representation you’re connecting from, i.e:

You have a representation of a server at

http://example.com/server1/
then your websocket connection goes to ws://example.com/server1/ for the live streaming events related to the server (or whatever) represented by the /server1/ url.

Cheers,
Ben

By: Matthew

Matthew — Sat, 22 May 2010 23:23:25 +0000

Very good tutorial, but I ran into one minor issue. If you’re just pasting the JavaScript part into an HTML file and pointing your browser at it, it won’t work. You’ll need to change line 10 of the python script to:

WebSocket-Origin: null\r\n\

And if you’re running it from a webserver; that line has to show the correct address and port that the webserver is running on.

By: Amy

Amy — Fri, 23 Apr 2010 18:20:32 +0000

I read lots of articles and tutorials describing how to code stuff and all too often they are cluttered with a bunch of fancy stuff that isn’t necessary for the solution. By describing the websocket server in this minimalistic way makes it easy to understand and extend! Thanks for sharing!

By: Joel Larsson

Joel Larsson — Fri, 02 Apr 2010 15:57:31 +0000

Nice tutorial, lets see if we can use this in dogvibes, http://hackr.se/code/dogvibes

/Joel