Re: WINDOW_UPDATE, or flow-control in general for async APIs, we either
follow the epoll pattern or we do need expose the buffer/window size to the
application. The latter is often very error-prone (in my experience).
Curious why there isn't a JSR for the client-side API.
On Thu, Sep 11, 2014 at 11:45 AM, Edward Burns <edward.burns_at_oracle.com>
wrote:
> Hello Experts,
>
> While discussing the design of the HTTP/2.0 client in Java SE 9 [1] we
> came upon the question of what HTTP/2.0 specific configuration
> parameters we need to expose in the API. So far Shing-Wai and I have
> just come up with
>
> Stream priority
> WINDOW_UPDATE
>
> Are there any others you think should be exposed in the Servlet 4.0 API?
>
> Thanks,
>
> Ed
>
>
> http://openjdk.java.net/jeps/110
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | 11 work days til JavaOne 2014
> | 7 work days til start of JSF 2.3 and Servlet 4.0
>