W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

[Bug 12917] "deflate-stream" should be an optional extension when establishing a connection

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Jun 2011 23:26:16 +0000
To: public-webapps@w3.org
Message-Id: <E1QZAKm-0006wg-8v@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12917

Adrian Bateman [MSFT] <adrianba@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |

--- Comment #4 from Adrian Bateman [MSFT] <adrianba@microsoft.com> 2011-06-21 23:26:15 UTC ---
The point of extensions is that they are not a mandatory part of the spec. They
are not required for interop. It is perfectly possible to make a client and
service work without deflate-stream. Just as the extension is optional for a
service, it should be optional for a client. I don't understand why this is an
interoperability nightmare - it's part of the extensibility mechanism in the
protocol.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 21 June 2011 23:26:17 GMT

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