Re: #445: Transfer-codings

On 4 April 2014 14:02, Amos Jeffries <squid3@treenet.co.nz> wrote:

> On 4/04/2014 3:39 p.m., Matthew Kerwin wrote:
>
>
>
> > The rank fulfils the same role as in the HTTP/1.1 TE header. The rank
> value
> > is an integer in the range 0 through 65,535, where 1 is the least
> preferred
> > and 65,535 is the most preferred; a value of 0 means "not acceptable".
> > ```
>
> rank == q-value yes? so retaining similarity with HTTP/1.1 by calling it
> a q-value would be better.
>

The HTTP/1.1 text I was ripping off says:

   When multiple transfer codings are acceptable, the client MAY rank
   the codings by preference using a case-insensitive "q" parameter
   (similar to the qvalues used in content negotiation fields, Section
<http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-26#section-5.3.1>
   5.3.1 <http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-26#section-5.3.1>
of [Part2 <http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-26#ref-Part2>]).
 The rank value is a real number in the range 0
   through 1, where 0.001 is the least preferred and 1 is the most
   preferred; a value of 0 means "not acceptable".


and the associated BNF is:

     t-codings = "trailers" / ( transfer-coding [ t-ranking ] )
     t-ranking = OWS ";" OWS "q=" rank
     rank      = ( "0" [ "." 0*3DIGIT ] )
                / ( "1" [ "." 0*3("0") ] )


That said, I found it by searching the text for "q".


-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/