W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: issue 85 - range unit extensions

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 28 Jul 2008 23:14:41 +0100
Cc: ietf-http-wg@w3.org
Message-Id: <B7807684-18A4-42F3-9C11-F33ADFB7974F@mnot.net>
To: "Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, Frank Ellermann <nobody@xyzzy.claranet.de>

Ah.

That was a straw-man, and definitely the weakest part of the proposal;  
we'd need to find the right BNF. It's a shame that they chose '=', I  
suppose we could do something like

other-range-unit ( SP / "=" ) CHAR*

Cheers,



On 28/07/2008, at 7:06 PM, Frank Ellermann wrote:

>
> Mark Nottingham wrote:
>
>> How is that incompatible?
>
> Your syntax offers:
>
> | ext-content-range-spec = other-range-unit SP CHAR*
>
> The MSDN example is:
>
> | Content-Range: rows=1-2; total=2
>
>> From that I guess that "rows" in <other-range-unit>,
> followed by "=" instead of SP.  But as I said, I've
> not the faintest idea what I'm really talking about.
>
> Frank
>
>


--
Mark Nottingham     http://www.mnot.net/
Received on Monday, 28 July 2008 22:15:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:53 GMT