Re: [hybi] [whatwg] HttpOnly cookie for WebSocket?

[Greg Wilkins <gregw at webtide.com>]

Ian,


I'm also curious that you say the WHATWG is still actively
working on the protocol (even though you also say that the
protocol has reached last call at the WHATWG)?

The WHATWG submitted the document to the IETF and surely
it was expected that IETF processes would be applied
to edit and refine the protocol and the document.
If the WHATWG continue to work on their own document,
that is only going to result in multiple specifications!

HTTP was "already shipping" and had "multiple servers"
available before RFC1945.    Then over a decade of
specification work took place before RFC2616 finally
gave us a truly scalable protocol that has now stood
for another decade and guided an unprecedented expansion
of usage.

So it is only to be expected that the websockets protocol
and specification will continue to evolve over the next
few years.

The question is, who will guide this evolution?

Surely when the WHATWG submitted the protocol to the
IETF they were passing the protocol from the WHATWG
process to the IETF process?


regards