Re: [hybi] I-D Action:draft-ietf-hybi-thewebsocketprotocol-01.txt

[Greg Wilkins <[e-mail]>]

On 2 September 2010 09:26, John Tamplin <[e-mail]> wrote:

> The problem is that the framing of v75, v76, v00, and v01 are
> incompatible.

Tell me about it!

>  If you want to write a server that interoperates with
> browsers implementing these drafts (I know at least v75 and v76 are in
> the wild), then you have to rely on heuristics to figure out which one
> you are talking to.

We tried initially just to support v75 waiting for a sane v00, but
users were having problems.  So we switched to v76 and got howls of
despair from v75 users.
So now Jetty supports both and we use the presence of Sec headers to
pick between v75 and v76 implementations.

I don't know of any wide deployments of the server, but I do know that
those experimenting with it have other constraints that prevent them
arbitrarily changing browsers at the same time they upgrade their
servers.

> Even if there isn't a version in the 1.0 spec,
> any attempt to get real-world data while the spec is changing means
> you either have a version number or you heuristically determine one --
> the latter is obviously more prone to error.

Exactly - currently there is no change in the handshake for 01 draft,
so I will have to inspect the first packet and guess.  Of course that
does not work if the server sends the first packet.


> I would suggest adding Sec-WebSocket-Draft: 01 to implementations of
> this draft, and that header will only be present before the spec is
> finalized.

thanks!