3 ms·
The real problem is text-based protocols, which are naturally quite flexible (and rather inefficient to parse). If HTTP headers were simply a single-byte identi
by userbinator 5y ago
The real problem is text-based protocols, which are naturally quite flexible (and rather inefficient to parse). If HTTP headers were simply a single-byte identifier[1], then e.g. 03 is Content-Length and there's no way to interpret that as anything else. I've made similar comments about such before: https://news.ycombinator.com/item?id=23582056 https://news.ycombinator.com/item?id=23582056
[1] A single byte is sufficient --- there have been far less than 255 headers defined since the beginnings of HTTP; maybe custom ones can be defined in an additional space, but a byte is actually already more than sufficient to convey the same information that would take dozens of bytes in the current text-based protocol.
- chii 5y agoso you're just describing what amounts to packets, which is basically like udp or tcp. The reason http is good is due to the text nature (along with whatever drawbacks associated with it being text).
- jamesfinlayson 5y agoThat'd be nice - no uppercase/lowercase mixups (or the need to support Referer and Referrer).
- tablespoon 5y ago> [1] A single byte is sufficient --- there have been far less than 255 headers defined since the beginnings of HTTP; maybe custom ones can be defined in an additional space, but a byte is actually already more than sufficient to convey the same information that would take dozens of bytes in the current text-based protocol. You're probably only talking about ones defined in something like an RFC. I'm pretty sure there are far more than 255 different HTTP headers in use just by my employer's in-house stuff. > more than sufficient to convey the same information that would take dozens of bytes in the current text-based protocol It's 2021, who cares about dozens of bytes? I'd wager that's far less than 1% of the size of most HTTP exchanges, and it means generic tooling can actually show you something useful for all that custom stuff it's guaranteed not to know the specifics of.
- userbinator 5y agoI don't see how you can get to more than 255, unless someone is using them in an incredibly stupid way. What really matters is the standard ones that everyone agrees on. The vendor-specific ones can be in their own space (e.g. 8xh and above), and if that's not enough, define an extension mechanism that adds a byte and you get 65535 different ones, which is definitely more than enough. It's 2021, who cares about dozens of bytes? That's the sort of attitude that got us Electron and all the other bloated web crap out there. A little bit adds up quickly, especially at the scale of the Internet.
- tablespoon 5y ago> I don't see how you can get to more than 255, unless someone is using them in an incredibly stupid way. What really matters is the standard ones that everyone agrees on. The vendor-specific ones can be in their own space (e.g. 8xh and above), and if that's not enough, define an extension mechanism that adds a byte and you get 65535 different ones, which is definitely more than enough. It's kind of ridiculous to argue for a one-byte address space in 2021, then kludging on an extension mechanism to handle the obvious fact that's too small. And even after that, you're still leaving everyone with ints instead of names. So we'll all get to ask ourselves "what header is 3849, again?" way more than we ever should. That's ignoring the fact that this proposal is totally DOA unless you can find a time machine to go back to 1989 and hit Tim Berners-Lee on the head with a pipe while he was writing the HTTP spec. >> It's 2021, who cares about dozens of bytes? > That's the sort of attitude that got us Electron and all the other bloated web crap out there. A little bit adds up quickly, especially at the scale of the Internet. There's about a light year between worrying about a dozen bytes and something like Electron.
- userbinator 5y agoIt's kind of ridiculous to argue for a one-byte address space in 2021, then kludging on an extension mechanism to handle the obvious fact that's too small. I'm saying that it's not too small. You still haven't mentioned anything about your use-case of needing several hundred(!?!?) different unique headers. 30 years of HTTP and so far there's been less than 100 defined. So we'll all get to ask ourselves "what header is 3849, again?" way more than we ever should. Note that even those who have only a very vague idea of what HTTP is, know what a 404 is; and probably 403 too. There's about a light year between worrying about a dozen bytes and something like Electron. Multiply that dozen bytes by however much traffic goes through the entire Internet... and it suddenly doesn't look small anymore.
- chtitux 5y agoThis is what HTTP/2 does with HPACK compression to compress headers and its "static table" [1] for common headers. There are 61 headers already defined in this table. [1] https://httpwg.org/specs/rfc7541.html#static.table.definition https://httpwg.org/specs/rfc7541.html#static.table.definitio...
- legulere 5y ago> A single byte is sufficient Just use variable length encodings like LEB 128