The Web is becoming faster as more and more web browsers and servers adopt HTTP/2. But support for the new protocol is still rough cut, and new performance bottlenecks are becoming apparent as people start using HTTP/2.
To give one example, server push in HTTP/2 is a promising feature but is hard to use in practice without the server knowing what the client has in its cache. To give another, due to the latency-sensitive nature of the protocol, a misconfigured load balancer becomes a major performance bottleneck.
Kazuho Oku, the author of the H2O HTTP/2 server (often referred to as the most sophisticated implementation of the protocol) as well as the author of the cache digests for HTTP/2 Internet-Draft, explains the various issues discovered by the server-side and the client-side developers of the protocol and the solutions invented to address them. Kazuho also covers upcoming standards such as TLS 1.3 and QUIC and their impact.
Kazuho Oku is a Japan-based software engineer currently working as a researcher of platform software and services for Cybozu, Japan’s largest groupware vendor. He is the original developer of Palmscape (aka Xiino, the oldest web browser for Palm OS), Japanize (a consumer-based web localization service), Pathtraq (one of the largest web stats service in Japan), and Q4M (a pluggable Message Queue for MySQL). Kazuho was named to the TR100 by Technology Review in 2002 and a Super Creator by the IPA, Japan, in 2005.
Comments on this page are now closed.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org