Awesome! Should be interesting to see a slew of new collaborative tools and games coming out soon!
WebSockets RFC is now official
11–20 of 47 posts
Re: WebSockets RFC is now official
#12Earlier quoted context omitted.
I let socket.io worry about that. Great library.
I agree about socket.io. It works quiet well for most of what I need. The only issue I have with is is I can't figure out if it now supports sending and receiving ArrayBuffers? Does anyone know anything about this? My use case involves sending model data to display in WebGL. Sending it any other way would be inefficient.
It's something we're currently working on. We're going to be integrating a XHR binary data fallback as well into our realtime engine.
Re: WebSockets RFC is now official
#13I look forward to pushing this to the absolute limit. Chat? Can we do something cool with voice? What about websites-as-desktop-software that started when Ajax got cool, but paused when developers ran into the limits of Ajax? How far can that now go? GPS services?
gps service? checked!
Well kind of. Last summer I did a road trip to newfoundland (canada) with a laptop, a gps and a webcam onboard [1]. The idea was to have people (friends and family) to follow our trip through a website to which I pushed webcam frames and gps coordinate in real time using websocket (socket.io) over my smarthphone. It was fun!
[1]: http://blog.rassemblr.com/2011/07/how-to-hack-a-road-trip-wi...
Re: WebSockets RFC is now official
#14Re: WebSockets RFC is now official
#15Yay! Looks like they fixed it. Now, it looks like it is a normal upgrade request so proxies, et al, should play nice. Yaaay!
Many proxies deployed today won't understand the upgrade header and in the case of an explicit proxy config will ignore the CONNECT operation if performed on 80 (rather than 443).
WebSockets works best over SSL.
Re: WebSockets RFC is now official
#16link to html version: http://tools.ietf.org/html/rfc6455
instead of the plain-text one: http://www.rfc-editor.org/rfc/rfc6455.txt
Re: WebSockets RFC is now official
#17Earlier quoted context omitted.
Quite literally. One of the most obvious applications of this is creating asynchronous multiplayer browser games.
Oh boy. Pretty soon we will need UDP sockets in the browser.
You can already do peer-to-peer UDP communication in a browser with Flash RTMFP protocol. If I remember right it was shipped with Flash 10, which got released 4 years ago.
Re: WebSockets RFC is now official
#18Incredible news. This day couldn't come soon enough.
Re: WebSockets RFC is now official
#19Earlier quoted context omitted.
Quite literally. One of the most obvious applications of this is creating asynchronous multiplayer browser games.
Oh boy. Pretty soon we will need UDP sockets in the browser.
WS is already kind of fire-and-forget. Socket.IO supports that, and can handle thousands of messages/second, I don't think that will be needed.
Re: WebSockets RFC is now official
#20What's the best option for using websockets with Python?
WSGI doesn't support it (http://librelist.com/browser//flask/2010/9/1/flask-and-webso...). gevent is an option (http://blog.pythonisito.com/2011/07/gevent-zeromq-websockets...), but would something like Mongrel2 be better (http://mongrel2.org/)?
UPDATE: There's also Juggernaut (http://flask.pocoo.org/snippets/80/), which uses node.js under the hood.