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
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
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
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
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
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 their own publishers and
subscribers, that is, they can't take a Flow.Publisher or Flow.Subscriber
provided by another reactive st
