RFR [11] 8197564: HTTP Client implementation - JEP 321

2018-04-05 Thread Sebastien Deleuze
Hi, I am currently implementing a draft support for JDK new HTTP client in Spring Framework 5 [1] (using JDK 10 for now) in order to be able to leverage it as a WebClient [2] engine. Our integration tests all pass with regular HTTP/1.1 webservices (we have not tested the HTTP/2 support yet), but

Re: RFR [11] 8197564: HTTP Client implementation - JEP 321

2018-04-05 Thread Michael McMahon
Sebastien, The answer depends on the particular HttpResponse.BodySubscriber/Handler implementation supplied to the sendAsync() call. Some of the simpler ones which return aggregate/completed objects like String, or byte[] do not appear to stream and the response body is not returned until afte

Re: RFR [11] 8197564: HTTP Client implementation - JEP 321

2018-04-05 Thread Chris Hegarty
Hi Sebastien, > On 5 Apr 2018, at 11:07, Sebastien Deleuze wrote: > > Hi, > > I am currently implementing a draft support for JDK new HTTP client in Spring > Framework 5 [1] (using JDK 10 for now) in order to be able to leverage it as > a WebClient [2] engine. Great that you are trying this

Re: RFR [11] 8197564: HTTP Client implementation - JEP 321

2018-04-05 Thread Sebastien Deleuze
Michael, Chris, Thanks for your feedback, indeed with PublishingBodySubscriber, it works also for streaming use cases and it provides the behavior I was trying to achieve. So +1 for inclusion of JDK-8201186 in JDK 11. On Thu, Apr 5, 2018 at 6:12 PM, Chris Hegarty wrote: > Hi Sebastien, > > > On