On Wed, 2025-05-21 at 17:00 -0700, Ryan Schmitt wrote: > Sorry I missed this, I've actually still been busy releasing the 5.4 > upgrade internally. I have a working implementation of Unix domain > socket support for the classic client and will do the async client > next. I was hoping for a series of 5.5 beta releases to give me some > time to put these features through their paces; I still need to run > 5.5 against our internal integration tests. In particular, the > changes > for redirects and the new support for HTTP/2 multiplexing could be > quite significant.
There is nothing stopping us from releasing feature releases more often. When can do 5.6 as soon as you are ready. Oleg > > On Thu, May 15, 2025 at 6:02 AM Oleg Kalnichevski <ol...@apache.org> > wrote: > > > > Folks > > > > There has been no feedback to the 5.5 alpha1 release and we have > > not > > added any more features to the 5.5 branch. > > > > Most of the new feature are considered experimental. I see no point > > waiting any longer. It will not improve anything considerably. > > > > I would like to propose HttpClient 5.5 GA be released soon, based > > on > > alpha1 and skipping the beta phase. > > > > Oleg > > > > > > > > On Mon, 2025-02-17 at 18:14 +0100, Oleg Kalnichevski wrote: > > > The Apache HttpComponents project is pleased to announce 5.5 > > > alpha1 > > > release of HttpComponents HttpClient. > > > > > > This is the first ALPHA release in the 5.5 release series. It > > > adds > > > several experimental features and improvements such as request > > > multiplexing over a shared HTTP/2 connection and the Classic API > > > facade > > > acting as a compatibility bridge between classic I/O client > > > services and the asynchronous message transport used internally. > > > > > > Notable changes and features included in the 5.5 series: > > > > > > * Improved conformance to RFC 7616 (HTTP Digest Access > > > Authentication). > > > > > > * The connection pool implementation acts as a caching facade in > > > front > > > of a standard managed connection pool and shares already leased > > > connections to multiplex message exchanges over active HTTP/2 > > > connections. Experimental. > > > > > > * Extended Auth API and improved authentication protocol logic to > > > support mutual authentication. > > > > > > * The Classic API facade acting as a compatibility bridge between > > > the > > > classic I/O client services (based on the standard InputStream / > > > OutputStream model) and the asynchronous message transport used > > > internally. Experimental. > > > > > > * HTTP/2 support for the Fluent Facade (via Classic API facade). > > > Experimental. > > > > > > > > > ------------------------------------------------------------------- > > -- > > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > > For additional commands, e-mail: dev-h...@hc.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
