[jw989]

This is cool, largely because of the functional perspective to dealing with pools of websockets. I personally think the next level for websockets infrastructure is building a paradigm for large pools of concurrent websocket connections.

Perhaps a microservces implementation with each step (handshake, broadcasting, http overhead) having their own cluster and communicating through channels.

[jkarneges]

Pushpin (http://pushpin.org) may be in line with what you're thinking. It separates connection management from backend logic. In fact the project itself is a handful of microservices (Mongrel2 is used as a separate process for the HTTP handling).

[timc3]

Uses GNU AFFERO Version 3 license - noted to save someone else from going from happily excited to disappointment.

[jkarneges]

Code that can be run, modified, and redistributed at no cost. There are worse deals. ;)

[jw989]

Wow this is very close to what I was saying. Thanks for this