3 ms·
> You don't need to know what kind of web server is running when you send a request and the WEB server don't need to know what kind of client is sending the req
by such12 4y ago
> You don't need to know what kind of web server is running when you send a request and the WEB server don't need to know what kind of client is sending the request to answer.
Exactly. It’s not an API - it’s a way to transfer arbitrary blocks of data. Applications that use http have to build an API on top.
That’s why it’s not even close to a valid comparison, and yet it has still become extremely complex over time.
> Flawed is still better than no solution.
This not the case. In many cases flawed solutions simply fail.
- peoplefromibiza 4y ago> It’s not an API - it’s a way to transfer arbitrary blocks of data Uh? API cannot transfer blocks of data? Again: this is not new, it's tedious, it's bureaucratic, it can be hairy, but it's not difficult.
- such12 4y ago> API cannot transfer blocks of data? This seems like a deliberate and silly misunderstand on your part. If you don’t realize that most API’s generally do more than simply transfer arbitrary blocks of data, then you have lied about your experience as a developer. HTTP is just a transfer protocol. It’s in the name.
- peoplefromibiza 4y ago> If you don’t realize that most API’s generally do more than simply transfer arbitrary blocks of data where did I say it? > HTTP is just a transfer protocol that's been hardly true since forever. POST, PUT, DELETE, PATCH etc ever heard of these verbs before?