Web Application Messaging Protocol: Difference between revisions

Revision as of 23:38, 25 March 2023

Revision as of 03:39, 17 May 2023

Line 11:

Message [[serialization]] assumes<ref>[https://github.com/tavendo/WAMP/blob/master/spec/basic.md#serializations WAMP serialization]</ref> integers, strings and ordered sequence types are available, and defaults to [[JSON]] as the most common format offering these. Implementations often provide [[MessagePack]] as a faster alternative to JSON, but at the cost of an additional dependency.<ref>{{cite web|url=https://ksdaemon.github.io/wampy.js/#description|title=Wampy default serializer is JSON, but it also supports msgpack as a serializer, but you need to include msgpack.js as dependency}}</ref>

To identify remote procedures and PubSub topics without conflicts, WAMP also needs an ID space allowing global assignment and resolution. Because the protocol is Web native - WebSocket being the preferred transport - [[Uniform resource identifier|URI]]s are used.

===Workflow===

WAMP is architectured around client–client communications, with a central software, the router, dispatching messages between them. The typical data exchange workflow is:<ref>[https://github.com/tavendo/WAMP/raw/master/spec/figure/sessions2.png WAMP internals bird view diagram]</ref>

* Clients connect to the router using a transport, establishing a session.