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 19:16:26 +0200
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>, "Maciej Stachowiak" <mjs@apple.com>, "Arthur Barstow" <art.barstow@nokia.com>, "Adrian Bateman" <adrianba@microsoft.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.vyzblofi64w2qv@annevk-macbookpro.local>
On Thu, 21 Jul 2011 19:02:31 +0200, Adrian Bateman  
<adrianba@microsoft.com> wrote:
> For platform features that directly affect web developers' pages that  
> might sometimes be true. However, compression is also optional in HTTP  
> and it
> doesn't appear to have caused problems or made some sites work and others
> not based on some dominant implementation.

Actually it has. You are pretty required to support it these days and you  
better be sure you Accept-Encoding header is formatted consistently.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Thursday, 21 July 2011 17:17:12 GMT

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