Web Application Messaging Protocol: Difference between revisions

Content deleted Content added
m Disambiguating links to Polyfill (link changed to Polyfill (programming)) using DisamAssist.
m Simplified sentence structure so that it becomes easier to read
Line 34:
As WAMP uses Websocket, connections can be wrapped in [[Transport Layer Security|TLS]] for encryption. Even when full [[confidentiality]] is not established, several mechanisms are implemented to isolate components and avoid [[man-in-the-middle attack]]s. Default implementations ensure that trying to register an already registered procedure will fail.
 
Routers can define realms as administrative domains, and clients must specify which realm they want to join upon connection. Once joined, the realm will act as a [[namespace]], preventing clients connected to onea torealm be able to do RPC and PubSubfrom using IDs defined in another for RPC and PubSub. Realms also have permissions attached, and can limit the clients to one subset of the REGISTER/CALL/PubSub actions available.
 
Some realms can be only joined by authenticated clients, using various authentication methods such as using [[X.509|TLS certificate]], [[HTTP cookie|cookies]] or a simple ticket.