Revision as of 05:38, 1 November 2015 edit Mild Bill Hiccup (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 175,657 edits →Routers: be setup → be set up ← Previous edit		Revision as of 13:07, 2 November 2015 edit undo AnomieBOT (talk \| contribs) Bots 6,858,452 edits m Dating maintenance tags: {{Says who}} Next edit →
Line 116: 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{{Says who\|date=November 2015}} as a swappable black box just like one would consider [[Apache HTTP Server\|Apache]] or [[Nginx]] for [[Hypertext Transfer Protocol\|HTTP]]: {\| class="wikitable"

Web Application Messaging Protocol: Difference between revisions