![]() So Windows Server 2019 brings connection coalescing to mitigate sharding. Like so often when you have a migration period from an older protocol to a newer version, there are trade-offs and workarounds to deal with the legacy way of doing things. ![]() Windows Server 2016 and the corresponding version of Windows 10 implemented HTTP/2 on both the server ( IIS) and the client side. For security, it supports only TLS 1.2 and newer, and it blacklists older cipher suites. It also compresses the header using HPACK, reducing the amount of data exchanged between servers and clients see more here. ![]() ![]() As a quick overview of what the new protocol brings, HTTP/2 multiplexes TCP (and TLS when using HTTPS) requests over a single TCP connection whereas 1.1 requires a dedicated connection for each request. The older version of HTTP (1.1) came out in 1999, so when HTTP/2 emerged in 2015, a lot had happened in between. In the next part, we'll cover software-defined networking (SDN) and Hyper-V networking improvements. In this first part, we'll look at HTTP/2, Cubic, and Low Extra Delay Background Transport (LEDBAT) for congestion management, Data Plane Development Kit (DPDK) for high-throughput applications, networking for Kubernetes on Windows, the Azure Network Adapter, and timekeeping. This two-part post will look at the networking enhancements coming in Server (and by extension, to Windows 10 since they share the same codebase).
0 Comments
Leave a Reply. |