![]() Whereas HTTP/1.1 and HTTP/2 use the Transmission Control Protocol ( TCP) as their data transport protocol, QUIC was designed from the beginning to work with User Datagram Protocol ( UDP). The goal is to have HTTP/3 become a standard for the internet on the order of HTTP/1.1 or HTTP/2. In 2018 QUIC was combined with the HTTP working group of the Internet Engineering Task Force (IETF) to create the HTTP/3 specification. QUIC was created at Google by Jim Roskind, who released the first version of the design specification in 2012. ![]() ![]() QUIC is an acronym for Quick UDP Internet Connections. The bottom line is that HTTP/3 is designed for greater efficiency in web communication. You'll read about these limitations and how HTTP/3 addresses them in a moment. HTTP/2 is fast, but it has design limitations that HTTP/3 addresses. The internet has an insatiable appetite for speed, particularly as the demand for video, continuous event messaging, and other types of streaming data proliferate to a broader set of applications. The driving force behind the advent of HTTP/3 is to make information traveling over the internet go faster in a more efficient manner.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |