QUIC 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. It does this by establishing a number of multiplexed connections between two endpoints using User Datagram Protocol (UDP), and is designed to obsolete TCP at the transport layer for many applications, thus earning the protocol the occasional nickname "TCP/2". QUIC improves performance of connection-oriented web applications that are currently using TCP. Īlthough its name was initially proposed as the acronym for "Quick UDP Internet Connections", IETF's use of the word QUIC is not an acronym it is simply the name of the protocol. Safari implements the protocol, however it is not enabled by default. Microsoft Edge (a derivative of Chrome) and Firefox support it. QUIC is used by more than half of all connections from the Chrome web browser to Google's servers. QUIC (pronounced "quick") is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google, implemented, and deployed in 2012, announced publicly in 2013 as experimentation broadened, and described at an IETF meeting.
0 kommentar(er)
