Hi,
Could you please review the following change for JDK-8157273?
http://cr.openjdk.java.net/~prappo/8157273/webrev.01/
This change addresses some WebSocket API refinements and enhancements from [1].
Currently WebSocket API allows only one scheduled but not yet sent message (i.e.
an outstanding
Hi,
On Thu, Jun 9, 2016 at 12:54 PM, Pavel Rappo wrote:
> Hi,
>
> Could you please review the following change for JDK-8157273?
>
> http://cr.openjdk.java.net/~prappo/8157273/webrev.01/
>
> This change addresses some WebSocket API refinements and enhancements from
> [1].
>
> Currently WebSocket
“I’ve been waiting for you”
(Speaking in Darth Vader’s voice)
> On 9 Jun 2016, at 13:38, Simone Bordet wrote:
>
> I'm not sure I understand all this.
>
> I thought the idea was that you always want *at most* one outstanding write.
> Multiple writes should be chained via CS.
> Concurrent
This test has been seen to fail intermittently. There is an assumption in the
test that the client-side will fill the outgoing TCP buffer by writing 1
megabyte
of data, allowing for the server-side to close the connection out from under
it. This is the crux of the test. By slowing down the writes
