Content deleted Content added
Line 1:
{{Advert|date=October 2016}}
'''WAMP''' is a [[WebSocket]] subprotocol registered at [[Internet Assigned Numbers Authority|IANA]],<ref>[https://www.iana.org/assignments/websocket/websocket.xml IANA protocols listing page]</ref> specified<ref>[https://github.com/tavendo/WAMP/blob/master/spec/basic.md WAMP basic profile specifications]</ref> to offer routed [[Remote procedure call|RPC]] and [[Publish–subscribe pattern|PubSub]]. Its design goal<ref>{{cite web|url=http://wamp.ws/why/|title=Using WAMP you can build distributed systems out of application components which are loosely coupled and communicate in (soft) real-time.}}</ref> is to provide an open standard for soft real-time message exchange between application components and ease the creation of [[loosely coupled]] architectures based on [[microservices]]. Because of this, it is a suitable [[enterprise service bus]] (ESB),<ref>[http://www.slideshare.net/KSDaemon/wamp-en-exported A few words about WAMP]</ref> fit for developing responsive Web applications or to coordinate multiple connected devices in the [[Internet of Things|IoT]].<ref>{{cite web|url=https://books.google.co.th/books?id=JPKGBAAAQBAJ&pg=PA172&lpg=PA172&dq=wamp+iot&source=bl&ots=8_zF1iZI_k&sig=2CgkqF4tlry5byIUXLiZjZVG2N8&hl=en&sa=X&ei=m0yyVN2JMI6QuASV3oLYBA&redir_esc=y#v=onepage&q=wamp%20iot&f=false|title=In this chapter [...] you will learn about the Web Application Messaging Protocol [...] which provide tools and services for
==Characteristics==
Line 118:
While routers can technically be embedded directly into the application code and some client libraries also provide a router, this architecture is discouraged by the specification.<ref>{{cite web|title= Brokers and Dealers are responsible for generic call and event routing and do not run application code.|url=https://github.com/tavendo/WAMP/blob/master/spec/basic.md#application-code}}</ref>
Since the router is a moving part, it is best used{{
{| class="wikitable"
| |||