RFR JDK-8157273: Simplify outgoing messages queueing policy in WebSocket API

[Pavel Rappo]

> On 13 Jun 2016, at 12:14, Simone Bordet <simone.bordet at gmail.com> wrote:
> 
> To me, pings (let's leave out unsolicited pongs) are an application
> mean to measure roundtrip; because they can be interleaved at the
> protocol level, I may be interested in knowing when they are fully
> written, but I would not make this interfere with message sending.
> Say for example you have a scheduler that sends pings every X seconds,
> you don't want an application to coordinate with this in order to send
> messages. The application will eventually coordinate with the onPong()
> response to tune the buffer size based on the roundtrip time, or
> things like that.

If you're talking about the application scheduling these Pings every X seconds,
then I have a question. Are we talking about constant rate here or constant
delay? If it's the former, then I wonder what the application should do if the
previous Ping at time (t) still hasn't been sent by the time (t + period)?

It's related to the following questions I've asked previously. 

1. Does "sendPing" have to wait until the CF returned by the previous
"sendText|sendBinary" has completed?

2. Does "sendPing" have to wait until the CF returned by the previous sendPing
has completed?