3 ms·
The need for such a protocol is to promote interoperable serviecs. Websockets just sends data around, but with protocols like WAMP it's possible to build router
by rektide 11y ago
The need for such a protocol is to promote interoperable serviecs. Websockets just sends data around, but with protocols like WAMP it's possible to build routers like Crossbar.io[1], where a bunch of backend services can talk to a front-end box that communicates with clients; it's the Vulcand (a HTTP message router) of WAMP world.
And that's the thing... websockets is terribly un-web: it doesn't talk about resources, with addresses, it's a glaringly ambiguous pipe that could have anything. Forming a websocket does do a content-negotiation pass, but there's nearly no concensus for what to expect. And this is an early contendor trying to give Websockets well known content forms to talk. Not just well known, but resourceful, addressed content too. Whereas with HTTP, we've had a long long history of creating interactable public APIs, this is something WAMP has to create, because Websockets is anti-web.
[1] https://github.com/crossbario/crossbar https://github.com/crossbario/crossbar