3 ms·
HTTP is closer to RPC. You always know the address of the routine to call, so it's not actually a message (except in HATEOAS, in which you first need to learn t
by ivan_gammel 10y ago
HTTP is closer to RPC. You always know the address of the routine to call, so it's not actually a message (except in HATEOAS, in which you first need to learn the next address from last API call).
Closest analogy is the message queue (e.g. ESB) like Active MQ or Rabbit MQ (and the whole JMS tech), in which you do actually send a message and infrastructure does actually figure out who will receive and process it.
- specialist 10y agoHTTP(S) is the opposite of RPC (meaning: message-based). Both SOAP and XML-RPC tried to remedy that.
- ivan_gammel 10y agoHow exactly it is opposite?
- specialist 10y agoDifference between document (message-passing) and RPC styles: http://stackoverflow.com/questions/9062475/what-is-the-difference-between-document-style-and-rpc-style-communication http://stackoverflow.com/questions/9062475/what-is-the-diffe... Replace SOAP with HTTP, since SOAP is just an ill-advised, unnecessary, redundant obfuscation layer on top of HTTP, and so contrast still applies.