4 ms·
> curl seems like a quite basic application It's an HTTP client. Here's 1 of 7 HTTP RFCs https://www.rfc-editor.org/rfc/rfc7230 https://www.rfc-editor.org/rfc/
by user3939382 4y ago
> curl seems like a quite basic application
It's an HTTP client. Here's 1 of 7 HTTP RFCs https://www.rfc-editor.org/rfc/rfc7230 https://www.rfc-editor.org/rfc/rfc7230
There are bigger specs like for wifi where it's thousands of pages, but I don't think you can classify a client that implements even half of the HTTP specs as basic.
- phendrenad2 4y agoIn other words, curl attempts to fully implement the RFCs, which have many, many edge cases and weird features, so a seemingly simple application balloons into a massive undertaking.
- theandrewbailey 4y agocurl is way more than HTTP. > curl supports about 26 protocols. We say "about" because it depends on how you count and what you consider to be distinctly different protocols. https://everything.curl.dev/protocols/curl https://everything.curl.dev/protocols/curl
- magicalhippo 4y ago> It's an HTTP client. Yeah that's what I mean, on the face of it there's not all that much platform specific code should be required for that. Sure handling all the edge cases of HTTP and whatnot isn't trivial, but almost all of that should be platform neutral so not relevant for this discussion. Now granted I know HTTP/2 and HTTP/3 are different beasts. But that's why I said it would have been nice with some concrete examples. It's always interesting to learn about issues and pitfalls you've never considered, or similar.