That said, I don't think the intent should be to support any old versions for any protracted amount of time. -00 has security vulnerabilities brought up by people on webkit-dev@ so from the Chrome side, we intend not to support -00 at all once we have -09 support available. All the makers of server-side code have already published versions compatibile with the latest draft, and IETF drafts are intended to expire after a fixed amount of time (-00 is already well past its expiration date).
-Ian On Thu, Jun 23, 2011 at 11:38 AM, Julian Reschke <julian.resc...@gmx.de>wrote: > On 2011-06-23 17:15, Simon Fraser wrote: > >> I'm surprised that the protocol has no facility for versioning. Is that >> really he case? Should it be considered for future versions of the spec? >> > > It does. > > <http://tools.ietf.org/html/**draft-ietf-hybi-**thewebsocketprotocol-09#** > section-11.11<http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-09#section-11.11> > > > > ______________________________**_________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/**mailman/listinfo.cgi/webkit-**dev<http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev> >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
