- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 7 Apr 2009 14:56:54 +1000
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Cc: Henrik Nordstrom <henrik@henriknordstrom.net>, Roy Fielding <fielding@gbiv.com>, Jamie Lokier <jamie@shareable.org>
- Message-Id: <96B041FE-74E2-4F5E-B334-14F9835E4025@mnot.net>
Haven't seen discussion on this for a while, seems like consensus is to drop multipart/byteranges as a delimiter. Any objection to that? On 12/12/2008, at 4:17 AM, Jamie Lokier wrote: > > Henrik Nordstrom wrote: >>> They aren't used that way. I don't know of any implementation >>> that uses the multipart delimiter to find the end of body (they >>> use CL, chunked, or a closed connection). >> >> Hmm.. you may be right. On a closer inspection I see that I misread >> some >> of the data. Sorry for the confusion. >> >> So it looks like dropping 4.4 ァ4 entirely may be an option. > > If it's possible to drop support for multipart/byterange delimited > messages, because it's not used anyway, that would be a really good > thing imho. It's an ugly, pointless, unused and probably poorly > implemented complication in message parsers. > > -- Jamie > -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 7 April 2009 04:57:35 UTC