Hi all, There were a lot discussions regarding Websockets few months (years?) back, before the RFC6455 was released and the hybi group defining the protocol was in pretty messy state. Now this technology is stable and coming mainstream with almost all browsers supporting it, so i think it's time to reopen the question for Twisted. There are many forks on Github from the original work of rlotun called txWebSocket. My branch may be the most advanced ( https://github.com/aprilmay/txWebSocket ). It works quite well for my purpose until now, even if it can surely be improved. It has both server and client, trial tests, basic support for extensions (eg compression and multiplexing are on the way from the hybi group) and i hope is efficient enough for most uses. There is also a project called Autobahn but it is not integrated with twisted.web (so one cannot serve standard HTTP and websockets from the same service out of the box) and was designed first to be a test suite for the development of the protocol. What are the opinions from the core team and other people in this list on this? Thanks, Philippe
On Oct 28, 2012, at 1:26 PM, Philippe May <phil.twisted-web@hanjinet.org> wrote:
Hi all,
There were a lot discussions regarding Websockets few months (years?) back, before the RFC6455 was released and the hybi group defining the protocol was in pretty messy state.
Now this technology is stable and coming mainstream with almost all browsers supporting it, so i think it's time to reopen the question for Twisted.
There are many forks on Github from the original work of rlotun called txWebSocket. My branch may be the most advanced ( https://github.com/aprilmay/txWebSocket ). It works quite well for my purpose until now, even if it can surely be improved. It has both server and client, trial tests, basic support for extensions (eg compression and multiplexing are on the way from the hybi group) and i hope is efficient enough for most uses.
There is also a project called Autobahn but it is not integrated with twisted.web (so one cannot serve standard HTTP and websockets from the same service out of the box) and was designed first to be a test suite for the development of the protocol.
What are the opinions from the core team and other people in this list on this?
The relevant link here is <http://tm.tl/4173>. There's a branch, and work is still ongoing there, with updates as recent as 3 days ago. Perhaps you should just Cc: yourself on that ticket and participate in development? -glyph
Great, thanks for the link! This ticket was pending for such a long time, good to see it's well alive. I'll see in what i can contribute in that branch, and hope that it will be merged in a release soon. Philippe Le 29 oct. 2012 à 02:16, Glyph a écrit :
On Oct 28, 2012, at 1:26 PM, Philippe May <phil.twisted-web@hanjinet.org> wrote:
Hi all,
There were a lot discussions regarding Websockets few months (years?) back, before the RFC6455 was released and the hybi group defining the protocol was in pretty messy state.
Now this technology is stable and coming mainstream with almost all browsers supporting it, so i think it's time to reopen the question for Twisted.
There are many forks on Github from the original work of rlotun called txWebSocket. My branch may be the most advanced ( https://github.com/aprilmay/txWebSocket ). It works quite well for my purpose until now, even if it can surely be improved. It has both server and client, trial tests, basic support for extensions (eg compression and multiplexing are on the way from the hybi group) and i hope is efficient enough for most uses.
There is also a project called Autobahn but it is not integrated with twisted.web (so one cannot serve standard HTTP and websockets from the same service out of the box) and was designed first to be a test suite for the development of the protocol.
What are the opinions from the core team and other people in this list on this?
The relevant link here is <http://tm.tl/4173>. There's a branch, and work is still ongoing there, with updates as recent as 3 days ago. Perhaps you should just Cc: yourself on that ticket and participate in development?
-glyph _______________________________________________ Twisted-web mailing list Twisted-web@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web
There is also a project called Autobahn but it is not integrated with
twisted.web (so one cannot serve
standard HTTP and websockets from the same service out of the box) and was
No, you can use Autobahn with Twisted Web https://github.com/tavendo/AutobahnPython/tree/master/examples/ => websocket/echo_site and with WSGI (i.e. Flask) https://github.com/tavendo/AutobahnPython/tree/master/examples/ => websocket/echo_wsgi Both does work with TLS and also supports not only Hybi-10+, RFC6455, but also Hixie-76 variants of WebSocket.
designed first to be a test suite for the development of the protocol.
No, the testsuite is a side project for Autobahn. Autobahn was designed to provide first-class WebSocket client and server support for Twisted. The testsuite has evolved into a "quasi industry standard": most projects use it to test for protocol compliance. Autobahn also provides RPC and PubSub on top of WebSocket: http://wamp.ws/. This is an officially registered WebSocket subprotocol and has implementations outside Twisted .. including 3rd party ones. Cheers, Tobias
participants (3)
-
Glyph -
Philippe May -
Tobias Oberstein