A deep-dive podcast episode covering HTTP/3 support coming in Java 26, featuring Oracle OpenJDK committers who built it. The discussion traces the evolution of Java's HTTP client from Java 9 (incubating) through Java 11 standardization, explaining why a new client was needed for HTTP/2. The bulk covers HTTP/3 and the QUIC protocol: why QUIC runs over UDP instead of TCP (head-of-line blocking, ossification, evolvability), the multiple RFCs implemented (QUIC, QUIC-TLS, congestion control, HTTP/3, QPACK), and the ~3-year implementation effort. Key practical details include the three H3 discovery modes (alt-svc, URI-only, any/optimistic), why HTTP/3 is not the default (UDP port overhead, timeout costs, API compatibility with the version enum), and future possibilities like DNS SVCB record-based discovery. The QUIC implementation remains internal and is not planned for public API exposure.
Sort: