5 ms·
HTTP/2 and HTTP/3 do not change the semantics of HTTP. That means you can run reverse proxies to server HTTP/1 services as /2 and/or /3 and vice-versa. As a r
by cryptonector 6y ago
HTTP/2 and HTTP/3 do not change the semantics of HTTP. That means you can run reverse proxies to server HTTP/1 services as /2 and/or /3 and vice-versa. As a result the transition will be a lot easier than the transition to IPv6. I expect that the transition in corporate networks will be faster -- the opposite of the IPv6 case -- because there is a lot of appeal to HTTP/3.
- the_duke 6y ago> because there is a lot of appeal to HTTP/3 I thought the primary appeal of HTTP/3 is for mobile clients, and bad connections in general, because it circumvents TCP head of line blocking and connections can persist across networks. That doesn't feel terribly relevant in corporate networks. (not disputing that it's not comparable to the v6 transition)
- cptskippy 6y agoHis claim of corporate appeal is completely unsubstantiated and I think when he says corporate he isn't referring to enterprise. Enterprises largely won't give two shits about HTTP/3. Just last week I took ownership of another department's decade old app written in VB.NET WinForms. The former dev team was putting the finishing touches on the C# WebForms refactor. It's been interesting taking a step back in time to Dev practices from 2008.
- cryptonector 6y agoThe appeal of H3 is smaller memory footprint.
- user5994461 6y agoYou realize that HTTP/2 is still nowhere near to being adopted by corporations? It's really far fetched to plan HTTP/3 and expect any adoption.
- cryptonector 6y agoThe fact that UDP involves much smaller PCBs than TCP alone will drive adoption of HTTP/3 because it will free up a fair bit of memory. More availability of HTTP version gateways in load balancers and other reverse proxies is all that's needed, and that's coming along.
- microcolonel 6y agoMore specifically no PCB, for UDP itself.
- cryptonector 6y agoIt's not nil. For "connected" UDP sockets, it's smaller than TCP's, but not nil because, well, buffers. And for non-connected UDP sockets there's still buffers. The main thing is that you can have much less buffer space because you might always be willing to drop packets. Ultimately you can have much lower memory pressure from those buffers and the smaller PCBs.
- moreati 6y agoProtocol Control Block for anyone else wondering https://www.oreilly.com/library/view/tcpip-illustrated/020163354X/ch22.html https://www.oreilly.com/library/view/tcpip-illustrated/02016...
- the8472 6y agoYou still need to keep your unacknowledged data buffered somewhere. If the kernel isn't holding it then it's in userspace.
- tialaramex 6y agoQualys' "SSL Pulse" says 47.1% of surveyed sites offered HTTP/2 and about 30% of surveyed sites offer TLS 1.3 Increasingly "corporations" out-source this problem to specialists who are only too pleased to use newer technologies with better performance and collect the same money.
- npiit 6y agoThe transition will be faster because of that a big chunck of the internet is gatewayed through a few big players (e.g. Cloudflare, AWS, CDNs, the new wave of static deployment services like Netlify and Zeit.co, big websites like google, facebook, netflix, etc...)
- awirth 6y agoThis is only mostly true, they do subtly change some semantics. As a motivational example, it is possible to encode a colon in a header name in http2 but not in http1.1, and this does not violate the RFC which only blacklists "\0\r\n".