3 ms·
If you're interested in API design the upcoming RFC standard might be of interest: https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-06 https://tools.ietf
by thexa4 7y ago
If you're interested in API design the upcoming RFC standard might be of interest: https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-06 https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-06
- corentin88 7y agoIt’s great that a standard will eventually be set on API. So many different ways of using them so far.
- avdempsey 7y agoWhile this link is very interesting, its advice doesn’t seem to completely pertain to the kind of “single deployment” APIs most of us are probably making. From the draft: “This document specifies best practices for writing specifications that use HTTP to define new application protocols, especially when they are defined for diverse implementation and broad deployment (e.g., in standards efforts).” That’s not to say there aren’t useful ideas here (I found it very interesting in its own right), but the provisions against fixed URL schemes is followed by no commercial HTTP API I’ve ever seen.
- rumanator 7y agoYour link is a bit stale. Here's a link to the latest version of the draft, published October 31st 2019: https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-09 https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-09