4 ms·
We're reinventing the wheel, yet again. Wasn't this what CORBA, XML-RPC, or SOAP was meant to solve? And then we all happily ditched them for loosely defined R
by phillmv 14y ago
We're reinventing the wheel, yet again.
Wasn't this what CORBA, XML-RPC, or SOAP was meant to solve? And then we all happily ditched them for loosely defined RESTy JSON because it was so goddamn easier.
I think TFA is describing a legitimate complaint; but I don't think the RESTy CRUD twitter exposes is all that difficult to abstract.
Amazon on the other hand…
- theatrus2 14y agoAmazon's protocols were clearly designed by a Java EE developer. Not that there isn't anything inherently wrong with them, and they are very flexible. They're also somewhat stuck with them based around the huge amount of code which interfaces with S3/AWS. There are some problems with no good solution, namely the signed parameters in Amazon's case. How do you sign JSON? Is there a "canonical" JSON format that will allow signing consistently, and verification? All the approaches I've seen are incompatible in some way. Client-side SSL is another solution, but its much less flexible (i.e., token-generated requests wouldn't be easy)
- userdeveloper 14y agoStuck with Java. Exactly.