Async-http-client has always been super-stable in the past and is being used by many other Java projects. I don't see any risk of being abandoned. The fact that activity was quiet is mostly related to this project being "complete" from a feature standpoint (which is good).
The alternatives are really not "async" and would cause a lot of performance regressions and other headaches. -- Matteo Merli <matteo.me...@gmail.com> On Thu, Feb 16, 2023 at 5:52 AM Asaf Mesika <asaf.mes...@gmail.com> wrote: > Oh. I looked at the commits, it seems pretty active to me. > > > On Thu, Feb 16, 2023 at 3:31 PM Zixuan Liu <node...@gmail.com> wrote: > > > I point to async-http-client. > > > > Although there is a recent update. > > > > Thanks, > > Zixuan > > > > Asaf Mesika <asaf.mes...@gmail.com> 于2023年2月16日周四 21:19写道： > > > > > On Tue, Feb 14, 2023 at 11:36 AM Zixuan Liu <node...@gmail.com> wrote: > > > > > > > Hi all, > > > > > > > > Our admin-client using the async-http-client [0] to request the web > > > > service, the async-http-client implements network request based on > the > > > > netty, which has very good performance, but this project is not very > > > > active. > > > > > > > > > > Netty - the most used network server in the world - is not very active? > > > > > > > > > > > > > > For security(library) reason or http feature(Follow up on future > > > > development), could we migrate to the jetty-client [1] from the > > > > async-http-client? The jetty project is very active, our web service > is > > > > built based on the jetty-server, so I think use the jett-client is a > > good > > > > idea, but migrating this can be a lot of work. > > > > > > > > Please let me know what you think. > > > > > > > > [0] - https://github.com/AsyncHttpClient/async-http-client > > > > [1] - https://github.com/eclipse/jetty.project/tree/jetty-9.4.x > > > > > > > > Thanks, > > > > Zixuan > > > > > > > > > >
