Lesson learnt, at least look for alternatives to see if the hammer you are about to wield is the right tool for the job

Show thread

This bit could also be called, “How English Evolves”

If the get-shit-done crowd wasn’t going to use SOAP, they still needed some standard way of doing things. Since everyone was using HTTP, and since everyone would keep using HTTP at least as a transport layer because of all the proxying and caching support, the simplest possible thing to do was just rely on HTTP’s existing semantics.
So that’s what they did. 1/2 …

Show thread

They could have called their approach Fuck It, Overload HTTP (FIOH), and that would have been an accurate name, as anyone who has ever tried to decide what HTTP status code to return for a business logic error can attest. But that would have seemed recklessly blasé next to all the formal specification work that went into SOAP.
2/3 …

Luckily, there was this dissertation out there, written by a co-author of the HTTP/1.1 specification, that had something vaguely to do with extending HTTP and could offer FIOH a veneer of academic respectability.
So REST was appropriated to give cover for what was really just FIOH. 3/3.

Show thread
Sign in to participate in the conversation

Be kind, be helpful or begone!