Hacker News Reader

I prefer to treat HTTP as a transport layer. A 200 means the transport succeeded but doesn’t indicate that the RPC succeeded.

View on HN

This makes no sense at all. "you got a response" means the transport succeeded, "it timed out" means the transport failed.

That’s a strong assertion. There’s plenty of status codes that indicate something bad happened at the HTTP level but don’t convey information about the RPC.

- 404 might mean the URL was wrong

- 405 might mean swapping POST with PUT

Not the http level… at the level above, the user of your api.

Both of these are simple programming errors. You might as well have used the wrong host or protocol for that matter

Reply on news.ycombinator.com