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

[Ian Hickson <[e-mail]>]

-whatwg; Please don't cross-post to the WHATWG list -- it causes threads 
to fragment since not everyone is subscribed to both lists and the WHATWG 
list rejects non-subscriber posts. Also, people on the WHATWG list didn't 
subscribe for political stuff, they just want the technical discussions.

On Fri, 29 Jan 2010, Greg Wilkins wrote:
> 
> 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 idea of a last call for comments is to get comments... those comments 
then have to be addressed. Then there's a call for implementations, which 
also results ein feedback, which also has to be addressed. And then 
there's the test suite that needs writing. Last Call therefore is not even 
half-way along the process.


> The WHATWG submitted the document to the IETF

I don't think that's an accurate portrayal of anything that has occurred, 
unless you mean the way my commit script uploads any changes to the draft 
to the tools.ietf.org scripts. That same script also submits the varous 
documents generated from that same source document to the W3C and WHATWG 
source version control repositories.


> 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!

HTML5, Web Storage, Web Workers, Microdata, 2D Canvas, Server Sent Events, 
Web Sockets API, Cross-Document Messaging, and Channel Messaging are all 
being developed by the W3C and the WHATWG together, and there's only one 
spec for each of those. Why would the IETF not be able to work with the 
WHATWG in the same way?


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

Goodness no. If you are referring to my publishing a draft using the IETF 
tools, that was (and is) done in the spirit of cooperation, just as is 
done with HTML5 with the W3C. I would be very happy to work with the IETF 
on Web Sockets, in conjunction with the WHATWG community, just as HTML5 
is developed as a joint effort.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'