Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
But maybe it's just me.
11–20 of 54 posts
Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
But maybe it's just me.
Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
bert-rpc.org
Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
Its been my experience that anything with Simple or Lightweight as one of the letters in the acronym is usually anything but.
Hmm, LDAP. I'd hate to meet HDAP.
I've just found myself working on a project like that for the first time, and saw this, and started wondering.
Earlier quoted context omitted.
bert-rpc.org
I hope not. Between Protobuf and Thrift, I don't see the point of adopting a less efficient, even more niche NIH serialization format and RPC protocol.
Using the Q & A style to introduce a topic works really well. I hope more people start writing like this.
Interoperability is a vitally important but hard problem. CORBA and then SOAP have been thoroughly adopted, then widely condemned. What's next?
JSON in HTTP GET/POST. It's more of a nuisance, but it forces you to face the network issues head-on, and code that reads JSON can't afford to make assumptions, so it ends up less brittle.
Its been my experience that anything with Simple or Lightweight as one of the letters in the acronym is usually anything but.
In the same way that the old communist states often had both 'democratic' and 'republic' in their over-long official names. Hmm, LDAP. I'd hate to meet HDAP.