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

Re: [#95] Multiple Content-Lengths

From: Adam Barth <w3c@adambarth.com>
Date: Mon, 20 Sep 2010 01:24:16 -0700
Message-ID: <AANLkTikQzdZAN9GGTn-D_qoa3MUUdLTGwoDRHfj58Fgo@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Anne van Kesteren <annevk@opera.com>, Willy Tarreau <w@1wt.eu>, HTTP Working Group <ietf-http-wg@w3.org>, Roy Fielding <fielding@gbiv.com>
I don't think a wire-level network protocol should impose normative
requirements on the user interface.  A non-normative recommendation
might be more appropriate.

Adam


On Mon, Sep 20, 2010 at 1:09 AM, Mark Nottingham <mnot@mnot.net> wrote:
> Thanks, Anne.
>
> Any thoughts on the most recent proposal (same e-mail)? It only requires that the user SHOULD be informed of the problem, which IMO could be satisfied by being made visible in a developer's error console, etc.
>
> Regards,
>
>
> On 20/09/2010, at 6:06 PM, Anne van Kesteren wrote:
>
>> On Mon, 20 Sep 2010 07:57:56 +0200, Mark Nottingham <mnot@mnot.net> wrote:
>>> Two replied that they have concerns about displaying errors to end users. If they come on-list and discuss their concerns, we can discuss this more.
>>
>> I was one of those if I remember correctly. End users just do not understand such error messages. And since they cannot do anything with them either showing error messages to end users will just make them confused, which gives them a bad product experience. It is exactly the same problem with asking users if they are okay with doing the request using the method CHICKEN to this other location. They'll just go "WTF" hit "OK" and hope it works, which is not that great really. Or worse, terminate the browser and start over.
>>
>>
>> --
>> Anne van Kesteren
>> http://annevankesteren.nl/
>
>
> --
> Mark Nottingham     http://www.mnot.net/
>
>
>
Received on Monday, 20 September 2010 08:25:20 GMT

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