W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [websockets] Making optional extensions mandatory in the API (was RE: Getting WebSockets API to Last Call)

From: Anne van Kesteren <annevk@opera.com>
Date: Thu, 21 Jul 2011 17:31:29 +0200
To: "ext Adrian Bateman" <adrianba@microsoft.com>, "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, "Maciej Stachowiak" <mjs@apple.com>, "Arthur Barstow" <art.barstow@nokia.com>
Cc: "Ian Hickson" <ian@hixie.ch>, "ifette@google.com" <ifette@google.com>, "jonas@sicking.cc" <jonas@sicking.cc>, "simonp@opera.com" <simonp@opera.com>, "Brian Raymor" <Brian.Raymor@microsoft.com>, "Takeshi Yoshino" <tyoshino@google.com>, "Greg Wilkins" <gregw@intalio.com>
Message-ID: <op.vyy6qr1764w2qv@annevk-macbookpro.local>
On Thu, 21 Jul 2011 17:26:21 +0200, Arthur Barstow <art.barstow@nokia.com>  
wrote:
> What do others (Anne?, Maciej?, ...) think about this issue?

I don't know enough about the WebSocket protocol, but optional web  
platform features suck. They will become mandatory following the typical  
"dominant implementation does it and we want to work on the same sites"  
scenario.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Thursday, 21 July 2011 15:32:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:46 GMT