Re: JEP 321: HTTP Client - Use of Flow.Subscriber and Flow.Publisher

2017-12-13 Thread Chris Hegarty
On 12/12/17 11:13, Chris Hegarty wrote: I filed the following JIRA issue to track this discussion and proposal. https://bugs.openjdk.java.net/browse/JDK-8193365 I'll start the process of bringing it into 10, unless there are any final comments. FTR, I'm happy where we ended up on this. An

Re: JEP 321: HTTP Client - Use of Flow.Subscriber and Flow.Publisher

2017-12-12 Thread Chris Hegarty
I filed the following JIRA issue to track this discussion and proposal. https://bugs.openjdk.java.net/browse/JDK-8193365 I'll start the process of bringing it into 10, unless there are any final comments. FTR, I'm happy where we ended up on this. -Chris. On 11/12/17 15:48, Chris Hegarty wro

Re: JEP 321: HTTP Client - Use of Flow.Subscriber and Flow.Publisher

2017-12-11 Thread Chris Hegarty
James, On 11/12/17 00:47, James Roper wrote: > Hi Chris, > > This looks like a straight forward way to solve the problem with minimal > disruption from the existing API. Can I make a few suggestions though? Of course, your input here is much appreciated. > We could add a contentLength parameter

Re: JEP 321: HTTP Client - Use of Flow.Subscriber and Flow.Publisher

2017-12-10 Thread James Roper
Hi Chris, This looks like a straight forward way to solve the problem with minimal disruption from the existing API. Can I make a few suggestions though? We could add a contentLength parameter to fromPublisher, to allow Flow.Publishers where the content length is known to be easily converted to B

Re: JEP 321: HTTP Client - Use of Flow.Subscriber and Flow.Publisher

2017-12-08 Thread Chris Hegarty
James, Thanks for taking the time to look at this, and sending your thoughts. On 08/12/17 00:30, James Roper wrote: > Hi all, > > I wanted to start a discussion about the use of Flow.Subscriber and > Flow.Publisher in JEP 321 (HTTP Client API). > > It seems that users are required to implement t