4 ms·

There is a standard for the "solution" in the article, passing the parameter on the body of a POST, like a remote call execution. That way you always return 200

There is a standard for the "solution" in the article, passing the parameter on the body of a POST, like a remote call execution. That way you always return 200 if the call is correct, and the content tells you the result or errors. The REST standard uses the error codes as part of it, and using a standard wrong will mean that you can't use most standard tools, which is probably worst.

aikah 4y ago
> The REST standard There is no such thing as a "REST standard" and that's why we've been having all these pointless arguments for the last 15 years. If Fielding really wanted web developers to use REST he would have wrote a normative spec about REST. Seems to me that REST was never about developers writing web API. The whole "smart client" capable of API discovery through "hyperlinks" is... a browser with a user clicking on those links. Except that API aren't consumed by browsers but other apps that are neither as smart nor complex.
- cxr 4y ago
  > Seems to me that REST was never about developers writing web API. You are correct. <https://news.ycombinator.com/item?id=23672561 https://news.ycombinator.com/item?id=23672561>