Re: [hybi] Ping/Pong body (was Re: TSV-Directorate review of draft-ietf-hybi-thewebsocketprotocol-07)

[Takeshi Yoshino <[e-mail]>]

Full body matching requirement has been introduced by
http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-03 for both
close and ping/pong. What was the original goal of this requirement for
ping/pong? Is it still valid? Full body matching requirement for close
frames has been thrown away after long discussion.

Now it looks like it's sufficient to have single boolean to indicate it's
nop or reply in application data.

Here's relaxed version.

foo and bar mean "any string"

a) implement heartbeat by diverting Pong
- Ping would be "Ping foo"
- to reply to "Ping foo", send "Pong \x00 bar" (bar is foo by default)
- to send unsolicited Pong, send "Pong \x01 bar"

b) implement heartbeat by diverting Ping
- to send Normal-Ping, send "Ping \x00 foo"
- to send NOP-Ping, send "Ping \x01 foo"
- to reply "Ping \x00 foo", send "Pong bar" (bar is foo by default)
- just ignore "Ping \x01 foo" when received

to adopt Bruce's idea, change "(bar is foo by default)" to "(bar is foo +
buz)". it implements echo and allows the receiver to send additional info.

I've removed unnecessary \x00 and \x01, but it's fine for me to keep them to
keep framing symmetric.

Takeshi