Re:Ask HN: What are the not-so obvious things to consider wh...
by abraae on Saturday November 18, 2017 @06:53PM
(#15731391)
From memory Facebook popularized this approach way back when.
[ Parent
| on HN ]
Re:Ask HN: What are the not-so obvious things to consider wh...
by dehrmann on Saturday November 18, 2017 @07:27PM
(#15731520)
This can make sense when you're doing batch requests and allow partial failures. I wish there were a standardized way of making batch requests--maybe even HTTP-level support. (It isn't such a big deal with HTTP2)
Re:Ask HN: What are the not-so obvious things to consider wh...
by rhizome on Saturday November 18, 2017 @09:24PM
(#15731891)
This can make sense when you're doing batch requests and allow partial failures.
Wouldn't that be a 206?
Re:Ask HN: What are the not-so obvious things to consider wh...
by detaro on Sunday November 19, 2017 @08:18AM
(#15733779)
No, 206 is only used with Range requests, when you try to get only some of the bytes of a larger resource.
There is 207, I think created by WebDAV, where you give back an XML document detailing the status of sub-requests. I feel like that'd be confusing in many contexts as well, and a clearly defined custom response is probably easier to handle for the user.