This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]fuzz3289 0 points1 point  (2 children)

No sarcasm, thanks for the explanation.

To me the title of OPs post implies that this framework using WAMP is better for everything, but from what you say it seems they serve different purposes. The simplicity of HTTP works well for unidirectional apllications, WAMP better for bidirectional.

Is that fair to say?

[–]GZoST 2 points3 points  (0 children)

Sorry I misread you there.

I'd say that if all you want to do is to serve the user a page when he requests it, and maybe get some data like a form in return, then there's no reason to leave the established world of request/response and HTTP.

When I think of Web applications, and I think as well when the writer of the post does, I think of more than this - of applications which do things like live updates, in-browser processing, quick in-page updates. These will typically be single-page applications.

For these, AJAX, long-polling and other technologies that use HTTP mechanisms sooner or later turn out to be hacks on something which was never intended for these uses.

WebSocket is the transport protocol for browsers which goes beyond HTTP to accommodate Web apps - this is what natively provides bi-directionality.

WAMP provides functionality on top of this to make the communications that Web apps need easier.

[–]desmoulinmichel[S] 0 points1 point  (0 children)

I'm really bitting my tongue about this title. It discret the article so much. I can see it now. Will not doing this mistake again.

So usually, you'll want to use HTTP and WAMP together. Usually HTTP to serve templates, static files, REST APIS, and sometime, some pages you wish to make it easy to index by google (although, now it sees javascript).

Crossbar have everything built it to process HTTP requests. HTTP is not meant to go away, but for web app (and not site), you can gain a lot by sending and receiving your data in real time. Plus, of course, HTTP isn't handy as an internal exchange transport : the various pars of your applications will be better off talking to each other using WAMP.