Websocket research

[makoConstruct]

There's a websocket protocol for Pubsub and RPC called WAMP. It's always given me the impression that it knows what it is and what it's doing far better than socket.io does. For one, socket.io hasn't got rpc baked in. (There's a project, https://github.com/capaj/socket.io-rpc, for adding it, but there's no documentation. There's an example, but it only bodes ill.). RPC (and a nice Promise API for it) is fairly important, so uh, I don't have much faith in socket.io at this point

The main WAMP imlementation for js clients is http://autobahn.ws/js/ , and I've heard good things.

There are a few server implementations http://wamp-proto.org/implementations/#routers, although it looks like they'll need a little bit of work eventually

• https://github.com/christian-raedel/nightlife-rabbit very badly maintained

• https://github.com/Orange-OpenSource/wamp.rt

• https://www.npmjs.com/package/wamp-server which doesn't seem to be listed. The author of wamp-server claims the other two js server impls have memory leaks, but they don't seem to have reported them... maybe I can see why.

The key thing to note: WAMP is not just javascript. Wamp is supported by lots of languages(or it at least makes an effort to be), so if we really care about decentralization, user freedom and federation, WAMP is already a part of our project.