- From: John Schneider <john.schneider@agiledelta.com>
- Date: Wed, 26 Aug 2009 12:52:38 -0700
- To: "'Henrik Nordstrom'" <henrik@henriknordstrom.net>, "'Mark Nottingham'" <mnot@mnot.net>
- Cc: <ietf-http-wg@w3.org>
Henrik, Thanks for asking this question. I was a little bit confused about the implications of merging the content-coding and transfer-coding registries, but your question and Roy's response have helped to clarify the intent of this action. Best wishes, John > -----Original Message----- > From: Henrik Nordstrom [mailto:henrik@henriknordstrom.net] > Sent: Wednesday, August 26, 2009 12:28 AM > To: Mark Nottingham > Cc: john.schneider@agiledelta.com; ietf-http-wg@w3.org > Subject: Re: Review of Content-Encoding: value token [exi] > > ons 2009-08-26 klockan 10:56 +1000 skrev Mark Nottingham: > > > That said, it would be good if what you do is done with an > eye towards > > the new regime, to reduce the amount of problems we see > down the road. > > In particular, it looks like the content-coding and transfer-coding > > registry will be one and the same, so it would help if you could > > design your registration with that in mind. > > They can not be entirely the same > > transfer-encoding must by definition be lossless or it will > fail HTTP operations, while content-encoding don't. > > Regards > Henrik >
Received on Wednesday, 26 August 2009 19:53:21 UTC