app from co-founder of Waze app:
Engie - Your Car Maintenance Solution
Connecting cars with service providers worldwide
Wednesday, October 09, 2019
Google QUIC protocol vs TCP
QUIC - Wikipedia
"QUIC (pronounced 'quick') is a general-purpose[1] transport layer[2] network protocol initially designed by Jim Roskind at Google,[3] implemented, and deployed in 2012,[4] announced publicly in 2013
While still an Internet Draft, QUIC is used by more than half of all connections from the Chrome web browser to Google's servers. Most other web browsers do not support the protocol.
Among other applications, QUIC improves performance of connection-oriented web applications that are currently using TCP.[2][9] It does this by establishing a number of multiplexed connections between two endpoints over User Datagram Protocol (UDP). This works hand-in-hand with HTTP/2's multiplexed connections, allowing multiple streams of data to reach all the endpoints independently, and hence independent of packet losses involving other streams. In contrast, HTTP/2 hosted on Transmission Control Protocol (TCP) can suffer head-of-line-blocking delays of all multiplexed streams if any of the TCP packets are delayed or lost.
"QUIC (pronounced 'quick') is a general-purpose[1] transport layer[2] network protocol initially designed by Jim Roskind at Google,[3] implemented, and deployed in 2012,[4] announced publicly in 2013
While still an Internet Draft, QUIC is used by more than half of all connections from the Chrome web browser to Google's servers. Most other web browsers do not support the protocol.
Among other applications, QUIC improves performance of connection-oriented web applications that are currently using TCP.[2][9] It does this by establishing a number of multiplexed connections between two endpoints over User Datagram Protocol (UDP). This works hand-in-hand with HTTP/2's multiplexed connections, allowing multiple streams of data to reach all the endpoints independently, and hence independent of packet losses involving other streams. In contrast, HTTP/2 hosted on Transmission Control Protocol (TCP) can suffer head-of-line-blocking delays of all multiplexed streams if any of the TCP packets are delayed or lost.
Subscribe to:
Posts (Atom)