<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jep321 on Devops Monk</title><link>https://devops-monk.com/tags/jep321/</link><description>Recent content in Jep321 on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/jep321/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP Client API (JEP 321): HTTP/2, Async, and Authentication</title><link>https://devops-monk.com/tutorials/java11/http-client-api/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/java11/http-client-api/</guid><description>Why a New HTTP Client? HttpURLConnection — Java&amp;rsquo;s HTTP API since Java 1.1 — has deep design problems:
Mutable shared state makes it error-prone in multithreaded code No built-in HTTP/2 support No built-in async; non-blocking requires manual thread management Clunky API: setDoOutput(true), getOutputStream(), connect() in sequence No support for reactive streams JEP 321 (Java 11) standardised the HTTP Client API that was incubating since Java 9. The new API lives in java.</description></item></channel></rss>