W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: #428 Accept-Language ordering for identical qvalues

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 22 Jan 2013 14:53:39 +0100
Message-ID: <50FE99E3.3020009@gmx.de>
To: Nicholas Shanks <nickshanks@nickshanks.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2013-01-22 14:40, Nicholas Shanks wrote:
> On 17 January 2013 09:14, Julian Reschke <julian.reschke@gmx.de> wrote:
>> On 2013-01-17 09:59, Roy T. Fielding wrote:
>>> than there are servers that implement language negotiation and
>>> actually want to resolve ties at random.
>>
>> They do not "want" to resolve at random; they do so because they have
>> implemented what the spec says. There's no reason to create an ordered list
>> structure when the spec says that an unordered list is sufficient.
>
> I think no implication of randomness should be permitted by the specifications.
> They should instead require that a deterministic process be used, and
> that, other than requests to services which explicitly exist to
> provide random results (e.g. Wikipedia's "Random Page" link), the same
> request should generate the same result providing nothing pertinent to
> the resource has changed on the server.
>
> Someone, I don't recall who, gave the example of a home page loading
> blog posts via AJAX, where the blog posts are available in two
> languages. Random selection between the variants, where (q * qs)
> values are equal for both languages, or are being ignored, would

Can you please give an example of clients sending these kind of header 
field values?

Clients that care can provide different qvalues, and as a matter of 
fact, they do.

 > ...

Best regards, Julian
Received on Tuesday, 22 January 2013 13:54:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 January 2013 13:54:12 GMT