On Tue, 2025-09-02 at 22:52 +0530, sreenivas somavarapu wrote: > Yes might be, but our application uses synchrous servlets and > changing it > to use asynchronous servlets is quite a challenging task as we have > some > business logic in the application which requires using of synchronous > servlets.
The classic facade runs on top of the async APIs, does it not? There is nothing stopping you from using the async APIs inside a servlet container with some sort of a compatibility layer of your own. > This is the main reason of trying Classic Facade APIs by > migrating from 4.2.x http client api implementation to 5.x > implementation. > Is there any setting or configuration which could help in file > downloads. The classic over async facade was never meant to be used for file download (especially multi 100K MiB files). Tweaking the size of intermediate content buffers may help somewhat but fundamentally InputStream / OutputStream based content processing is not well suited for event driven i/o and is always bound to be slower that the native classic i/o or the native event-driven i/o. Oleg > > Sreenivas > > On Tue, 2 Sept, 2025, 22:34 Oleg Kalnichevski, <[email protected]> > wrote: > > > On Tue, 2025-09-02 at 22:25 +0530, sreenivas somavarapu wrote: > > > Hi Oleg, > > > > > > This is a sample program to demonstrate the behavior. Actual > > > application is > > > a servlet (Which internally uses HTTPClient APIs to access > > > different > > > server > > > interfaces including but not limited to file servers i.e., this > > > is a > > > frontend high secure server available to a team of people who > > > doesn't > > > have > > > internet access). We wanted to support accessing HTTP/2 only > > > servers > > > using > > > this Application which is why we are trying the new Classic > > > Facade > > > API. > > > > You should be using the async APIs directly. > > > > Oleg > > > > > > ------------------------------------------------------------------- > > -- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
