Re: issue 85 - range unit extensions

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 UTC