> On 5 May 2016, at 00:20, Jitendra Kotamraju wrote:
> >
> > * I see that there is an issue for autoponging. May be this falls under
> it. The default impl of onPing() doesn't send PONG for *every* received
> PING.
>
> Yes, that's correct. The default imp
* I see that there is an issue for autoponging. May be this falls under it.
The default impl of onPing() doesn't send PONG for *every* received PING.
Since it is against the protocol semantics, it forces all applications to
override the default onPing() impl. Is that right ?
It seems to me that th
>
>
>
> You see there'a thing. That's why I didn't do it immediately. For example
> let's
> consider a "Sec-WebSocket-Extensions" (a very good illustrative example.)
> RFC 6455 states it very clearly [1]:
>
> The |Sec-WebSocket-Extensions| header field MAY appear multiple times
> in an HTTP
