What is WAMP (Web Application Messaging Protocol)?

Asked

Viewed 195 times

3

I’ve been studying a little bit about Websockets and while researching how to do channel structure or push, I came across the term WAMP.

It seems to me, WAMP is a protocol or subprotocolo of a Websocket connection.

I would like to know: What is in detail the WAMP?

Do not confuse with Wamp software used to run Mysql, Apache and PHP on Windows.

  • I think this footnote deserves a bigger highlight. I almost mark as duplicate

  • https://en.wikipedia.org/wiki/Web_Application_Messaging_Protocol

  • For those arriving here, this is the WAMP @Wallacemaxters is talking about: https://en.wikipedia.org/wiki/Web_Application_Messaging_Protocol?wprov=sfti1

  • I took most of the information I found about it and translated. Difficult content search by fault of the already existing tool.

  • 1

    @Jeffersonquesado with the title edition already helps

  • And who gave the negative could also clarify what can be improved!

Show 1 more comment

1 answer

7

Wamp

WAMP is a byproduct of Websocket registered in IANA, specified to offer routed RPC and Pubsub. Its design goal is to provide an open standard for real-time messaging between application components and facilitate the creation of slightly coupled microservice-based architectures. It is suitable for developing responsive web applications or for coordinating multiple connected devices on the Iot.

Pubsub

In software architecture, Publish-subscribe is a messaging pattern where message senders, called Publishers, do not program messages to be sent directly to specific receivers, called subscribers, but categorize published messages into classes without knowing which subscribers. Similarly, subscribers express interest in one or more classes and only receive messages that are of interest, without knowledge of which Publishers.

Subprotocols

Think of a subprotocolo as a custom XML schema or a doctype statement. You’re still using XML and its syntax, but you’re also constrained by a structure that you agreed to. Websocket’s subprotocolos are just like that. They don’t present anything fancy, they just establish structure. As a doctype or schema, both parties must agree to the subprotocolo; unlike a doctype or schema, the subprotocolo is implemented on the server and cannot be routed externally by the client.

Sources

Wamp - https://en.wikipedia.org/wiki/Web_Application_Messaging_Protocol

Pubsub - https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern

Subprotocols - https://developer.mozilla.org/en-US/docs/WebSockets/Writing_WebSocket_servers

  • 2

    Where are you translating from? It’s always good to put the search source

  • Unintentionally I had clicked on submit, before finishing my translation. Sorry, all fixed

Browser other questions tagged

You are not signed in. Login or sign up in order to post.