em-websocket

SockJS is definitely a reasonable choice as a base. At Pusher we use a fork of SockJS for HTTP fallback but we actually use em-websocket [1] (ruby) for our WebSocket API. Given the opportunity we'd probably move away from SockJS to something much simpler because we only want the HTTP fallback part and it only handles < 8% of our connections. If you _only_ want WebSocket connections with no HTTP fallback then Faye WebSocket [2] may be an option. But any production application is going to require fallback for older browsers and pesky proxies/firewalls. Faye [3] is solid (obviously used Faye WebSocket), has implementations in Node and Ruby, but is a PubSub solution. I'd kinda argue that any real-time app needs at least PubSub functionality anyway. The ws Node module [4] is apparently "The fastest RFC-6455 WebSocket implementation for Node.js

https://gist.github.com/crertel/7244841 There you go--left out the boring HTML scaffolding (original chat example modified from here: https://github.com/igrigorik/em-websocket). EDIT: It's super MVP, but the concept is there. A very, very simple addition would have the server echo back to the clients the lat/long pairs in question to dynamically update, say, a Google Maps window. For real usage, I'd use a PostGIS query--something like this: http://unserializableone.blogspot.com/2007/02/using-postgis-... . EDIT2: Looks like we're both Texans--if you're ever in Houston, I'd be glad to grab a beer with you.

Great stuff. Just for sake of completeness, you can basically copy-paste that code into Ruby as well via em-websocket: http://github.com/igrigorik/em-websocket Also, to avoid some of the callback muck that a few have brought up: http://github.com/igrigorik/em-synchrony (same idea, closures + coroutines to abstract the callbacks).