Googles new protocol using UDP instead of TCP.
https://ma.ttias.be/googles-quic-protoc ... b-tcp-udp/
HTTP/2 is too slow. Now we have QUIC.
-
- Rank VI - Professional
- Posts: 596
- Joined: Mon Jun 09, 2008 2:12 pm
- Location: Fargo, ND
-
- Site Admin
- Posts: 3785
- Joined: Sat Dec 11, 2004 9:23 am
- Location: Near Dallas, TX
Re: HTTP/2 is too slow. Now we have QUIC.
Thanks! That was a great read.
Now only if web developers don't find more ways to bloat up their pages and nullify the speed and bandwidth improvements of QUIC.
Now only if web developers don't find more ways to bloat up their pages and nullify the speed and bandwidth improvements of QUIC.
Albert Wiersch, CSS HTML Validator Developer • Download CSS HTML Validator FREE Trial
-
- Rank VI - Professional
- Posts: 596
- Joined: Mon Jun 09, 2008 2:12 pm
- Location: Fargo, ND
Re: HTTP/2 is too slow. Now we have QUIC.
This was part of Issue 6. You can view or signup here: https://perf.email/
Rick
-
- Site Admin
- Posts: 3785
- Joined: Sat Dec 11, 2004 9:23 am
- Location: Near Dallas, TX
Re: HTTP/2 is too slow. Now we have QUIC.
Thanks.... only twice a month? I think I can handle that (make time for) so I signed up.
Albert Wiersch, CSS HTML Validator Developer • Download CSS HTML Validator FREE Trial
-
- Rank VI - Professional
- Posts: 596
- Joined: Mon Jun 09, 2008 2:12 pm
- Location: Fargo, ND
-
- Rank VI - Professional
- Posts: 726
- Joined: Mon Dec 13, 2004 1:50 pm
- Location: Tannhauser Gate
Re: HTTP/2 is too slow. Now we have QUIC.
Thanks for that.
That syn/ack triple handshake is clearly a problem.
Notes:
1. Wireshark (naturally) can handle QUIC packets.
2. The site has an RSS feed (implemented primitively) so you don't even need to sign up for email if you use feeds.
That syn/ack triple handshake is clearly a problem.
Notes:
1. Wireshark (naturally) can handle QUIC packets.
2. The site has an RSS feed (implemented primitively) so you don't even need to sign up for email if you use feeds.