RFR JDK-8157273: Simplify outgoing messages queueing policy in WebSocket API
Pavel Rappo
pavel.rappo at oracle.com
Tue Jun 14 11:26:35 UTC 2016
> On 13 Jun 2016, at 12:14, Simone Bordet <simone.bordet at gmail.com> wrote:
>
>> Should the application be in charge of chopping outgoing messages in chunks in
>> order to provide better responsiveness when needed?
>
> Not sure what you mean here.
What I meant here was that Ping's latency doesn't depend on some kind of magic.
Implementation and/or application has to chop messages/fragments into more
fragments of a certain size *beforehand* to provide more places a control frame
can be injected to.
If a giant message/frame has been being sent, there's nothing can be done to
interject a control message quickly.
If we say a partial message corresponds to 1+ frames on a wire than both
implementation and the application can contribute better responsiveness. If we
say a partial message corresponds to exactly 1 frame, than all the burden of
chopping is on the application. In this case the responsiveness is independent
from an implementation.
More information about the net-dev
mailing list