Zixuan, Il giorno mar 14 feb 2023 alle ore 10:36 Zixuan Liu <node...@gmail.com> ha scritto: > > 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. > > 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.
I think that this makes sense. We will have to do it very carefully, especially when dealing with errors. A new library may report errors in a slightly different way and that may have an impact. Also we can do this kind of changes only on a major release, say 3.0.0 or 3.1.0 but this is not a big problem Users that use the non-shaded Pulsar client dependencies will have to deal with this change, but it is doable I wonder if we could use the Java HTTP client that is available on modern JDKs in case we switch to requiring JDK11 on the client Less dependencies is always a good choice for many reasons Enrico > > 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
