juggernaut

Socket.IO seems to be the most popular and active WebSocket emulation library. Juggernaut uses it to create a complete pub/sub system. Faye is also popular and active, and has its own javascript library, making its complete functionality comparable to Juggernaut. Juggernaut uses node for its server, and Faye can use either node or rack. Juggernaut uses Redis for persistence ( correction: it uses Redis for pub/sub), and Faye only keeps state in memory. Is everything above accurate? Faye says it implements Bayeux -- i think Juggernaut does not do this -- is that because Juggernaut is lower level

I'm building a real time game, mostly chat based, and I need to have many of these chats running concurrently, receiving and sending data through web sockets. I have been told that instead of spawning one process per game, I should have one process with one thread per game (maybe using Event Machine). I'm using Juggernaut for the sockets part, it lets me send data to all the players in a game by using a publish/subscribe system: each player subscribes to one game. But how do I send data from each player to that particular game? I was thinking that I could send the game ID or channel ID from

I am trying to build a small site with the server push functionality on Flask micro-web framework, but I did not know if there is a framework to work with directly. I used Juggernaut , but it seems to be not working with redis-py in current version, and Juggernaut has been deprecated recently. Does anyone has a suggestion with my case? Peter Hoffmann Have a look at Server-Sent Events . Server-Sent Events is a browser API that lets you keep open a socket to your server, subscribing to a stream of updates. For more Information read Alex MacCaw (Author of Juggernaut) post on why he kills