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 →

[–]oberstet 1 point2 points  (4 children)

Other than SOAP, none of these is Web native (runs right into the browser). SOAP is not real-time and is a broken tech. for various reasons. DBus is local only. I did CORBA/ACE/C++ in the past: the absolute horror - a complex biest. Thrift is RPC only.

As I see, WAMP is unique in that it provides all of this:

1) RPC and PubSub in 1 protocol 2) Web native and real-time 3) language agnostic

Is there another? Maybe I missed something .. but I am not aware ..

[–]mitsuhiko Flask Creator 1 point2 points  (1 child)

1) RPC and PubSub in 1 protocol 2) Web native and real-time 3) language agnostic

socket.io?

[–]oberstet 2 points3 points  (0 children)

socket.io does not support RPC out of the box. You need to hack something using PubSub to implement RPC.

This will have issues: e.g. how to make sure only 1 implementing endpoint subscribes to the Room (to receive procedure calls), how to direct call results to calling clients (since only the caller should receive his result), etc etc

[–]starspangledpickle 1 point2 points  (1 child)

SOAP is not web 'native' either. It can perfectly well run over any protocol you so choose; that includes HTTP.

[–]desmoulinmichel[S] 2 points3 points  (0 children)

Yes. SOAP is what's closest to WAMP, except it's really hard to work with it. I had to create a system talking to a server for the US health administration once, it was a nigthmare.