HTTP/3
1.Part 1: HTTP/3 History And Core Concepts 1
You may have read some blog posts or heard conference talks (on this topic) and think you know the answers.당신은 이 주제에 관해 어떤 블로그 글을 읽었거나 컨퍼런스 발표를 들어봤을 것
2.Part 1: HTTP/3 History And Core Concepts 2
One question (I’ve often encountered) / is, “Why do we need HTTP/3 so soon after HTTP/2, which was only standardized in 2015?” "내가 자주 만나는 질문 중 하나는, 20
3.Part 1: HTTP/3 History And Core Concepts 3
As a second example, TCP sees all of the data it transports as a single “file” or byte stream, even if we’re actually using it to transfer several fil
4.Part 1: HTTP/3 History And Core Concepts 4
What Is QUIC? You might be wondering why this matters? 너는 왜 이 문제가 중요한지 궁금해할 수 있을 것이다. Who cares if these features are in HTTP/3 or QUIC? 이러한 기능들이 HTT
5.Part 1: HTTP/3 History And Core Concepts 5
The Big Changes So, how exactly does QUIC improve upon TCP, then? 그렇다면 TCP에서 QUIC는 정확히 어떻게 개선됩니까? What is so different? 무엇이 다르니? There / are / sever
6.Part 1: HTTP/3 History And Core Concepts 6
The second big difference between TCP and QUIC /is/ a bit more technical, and we/ will explore/ its repercussions in more detail in part 2.TCP와 QUIC의
7.Part 1: HTTP/3 History And Core Concepts 7
Let’s take a closer look at the difference: 차이점을 자세히 살펴보겠습니다. However, there is a problem on the TCP side. You see, because TCP is a much older proto
8.Part 1: HTTP/3 History And Core Concepts 8
QUIC SUPPORTS CONNECTION MIGRATION The third major improvement in QUIC is the fact that connections can stay alive longer. >#### Did You Know? We oft
9.Part 1: HTTP/3 History And Core Concepts 9
A new TCP (and possibly TLS) handshake has to be executed to set up a new connection, and, depending on the application-level protocol, in-process act
10.Part 1: HTTP/3 History And Core Concepts 10
QUIC IS FLEXIBLE AND EVOLVABLE A final aspect of QUIC is that it’s specifically made to be easy to evolve. This is accomplished in several different w
11.Part 2: HTTP/3 Performance Features 1
Welcome back to this series about the new HTTP/3 protocol.새로운 HTTP/3 프로토콜에 대한 이 시리즈로 돌아온 것을 환영합니다.In part 1, we looked at why exactly we need HTTP/3 a
12.Part 2: HTTP/3 Performance Features 2
Congestion Control One aspect of performance is about how efficiently a transport protocol can use a network’s full (physical) bandwidth (i.e. roughly
13.Part 2: HTTP/3 Performance Features 3
This is an extremely oversimplified explanation of congestion control. In practice, many other factors are at play, such as bufferbloat, the fluctuati
14.Part 2: HTTP/3 Performance Features 4
Did You Know? > The official QUIC Recovery RFC 9002 specifies the use of the NewReno congestion-control algorithm. While this approach is robust, it’s
15.Part 2: HTTP/3 Performance Features 5
0-RTT Connection Set-Up A second performance aspect is about how many round trips it takes before you can send useful HTTP data (say, page resources)