Per the HTTP spec, chunked encoding may not be needed if "Connection:
close" is set and the TCP connection will be closed (FIN) to complete the
response body.
I am yet to write a test for this but the javadoc needs to address this
behavior..
This behavior can be supported using the existing API,
On Mon, Aug 22, 2016 at 12:56 AM, Michael McMahon <
michael.x.mcma...@oracle.com> wrote:
> There is an updated version of the HTTP client API doc [1] and a specdiff
> [2] showing the changes
> proposed from the current version in JDK9 dev.
>
> The main changes are:
>
> 1) The request and response
to invent another style IMO.
- Wenbo
On Fri, Jul 31, 2015 at 11:52 AM, Simone Bordet simone.bor...@gmail.com
wrote:
Hi,
On Fri, Jul 31, 2015 at 8:37 PM, Wenbo Zhu wen...@google.com wrote:
Or we follow the NIO2 model (readiness),
Please no ! :)
Ignoring the epoll part, is the issue
On Fri, Jul 31, 2015 at 11:32 AM, Simone Bordet simone.bor...@gmail.com
wrote:
Hi,
On Fri, Jul 31, 2015 at 7:54 PM, Wenbo Zhu wen...@google.com wrote:
Thanks for the update.
===
Is WebSocket out of the scope now?
== async streams
I.e. how bodies are to be read/written
I am new to the JEP process. Has there been any update on this work? Is
there an API proposal to look at?
Thanks,
Wenbo
JEP 110: HTTP 2 Client*mark.reinhold at oracle.com http://oracle.com*
mark.reinhold
at oracle.com
