3 ms·
I don't understand your point about third-party clients. APIs defined in .proto files can have both clients and servers implemented by anybody.
by euyyn 10y ago
I don't understand your point about third-party clients. APIs defined in .proto files can have both clients and servers implemented by anybody.
- daliwali 10y agoAPIs defined in XMLRPC, CORBA, SOAP, et al, can have clients and servers implemented by anybody. Programmers don't seem to learn from history and struggle with thinking over time. These formats worked well in a time when a single party (or second party) controls the server and client, when services were very consolidated. Now that the web is becoming more and more centralized and closed, it follows that RPC is making a comeback: widespread interoperability is not much of a concern.
- euyyn 10y agoSorry but you're not addressing your own point: > RPC is a great fit if you are constrained to a single vendor and don't care about third-party clients If I'm not constrained to a single vendor, and care about third-party clients, what makes RPC a bad fit? In specifics, not vague historical comparisons.