- From: Robin Berjon <robin@w3.org>
- Date: Mon, 03 Mar 2014 20:57:53 +0100
- To: Andrea Giammarchi <andrea.giammarchi@gmail.com>
- CC: "public-nextweb@w3.org" <public-nextweb@w3.org>
On 03/03/2014 19:21 , Andrea Giammarchi wrote: > Quickly my thoughts on this: > I believe there is no endpoint in the real world that is not capable of > inflating, or un-gzipping any content so I'd skip the "check the server" > part since you know who you are sending data to because this needs to be > stored or analyzed in there, accordingly the end point needs to know > what kind of data is receiving and since it supports already files, I > don't see concrete problems in supporting any sort of compressed binary > with a Content-Type that will be parsed after decompression. The problem is not being able to support, the problem is being ready to support. What implementations do today is that they just mostly read off a buffer (if not STDIN) and parse that without caring about Content-Encoding. We absolutely can't start to change that without breaking everything. -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 3 March 2014 19:58:01 UTC