IETF Logo Mail Archive

Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR

James M Snell <jasnell@gmail.com> Wed, 19 June 2013 18:06 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDD5D21F979E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 19 Jun 2013 11:06:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.554
X-Spam-Level:
X-Spam-Status: No, score=-10.554 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEF0agHFv1BJ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 19 Jun 2013 11:06:16 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 09A3521F9BDB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 19 Jun 2013 11:06:16 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UpMlV-0006N8-4Q for ietf-http-wg-dist@listhub.w3.org; Wed, 19 Jun 2013 18:05:53 +0000
Resent-Date: Wed, 19 Jun 2013 18:05:53 +0000
Resent-Message-Id: <E1UpMlV-0006N8-4Q@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UpMlH-0006LT-W1 for ietf-http-wg@listhub.w3.org; Wed, 19 Jun 2013 18:05:40 +0000
Received: from mail-vb0-f47.google.com ([209.85.212.47]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1UpMlH-0007jU-1S for ietf-http-wg@w3.org; Wed, 19 Jun 2013 18:05:39 +0000
Received: by mail-vb0-f47.google.com with SMTP id x14so3893848vbb.6 for <ietf-http-wg@w3.org>; Wed, 19 Jun 2013 11:05:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SWZTqq0QKYK1ik9cFOQi/1sX6Qz2XbWyZL4uzeFiemI=; b=cDNY+L4lHi6yxqX6wV4yg6BzF1J7HtuMgi2HegOjK2ChrnACt6HmQTj6KxtcJXlTj9 e49A4Ywm1FpYZLCekd1iQvLI/7CFuVE1wZD5aKJv8Hog4BUzIb91gvC/ys7gmk/OCBt9 HvA5UYZ11wd1KbRI82kqbTUPm2CTrJpvuRdyqTA2jHdMsCDhPadoSRmAuhjYzR33ujXj Vo3ZGv1Qz1LTlfohMlhgGolzR1/f3H5BAhf98w6F+OAenQxt0uXTToXyIeZ0SZt6z9sy vtQE/h3Kq6XeQrD6S8P+mTpvxjshedBB0fCt9KGdpzVhnV8wuk10Ewz3P+LexIzSAIWH e5GA==
MIME-Version: 1.0
X-Received: by 10.52.186.129 with SMTP id fk1mr1088070vdc.66.1371665113182; Wed, 19 Jun 2013 11:05:13 -0700 (PDT)
Received: by 10.58.47.8 with HTTP; Wed, 19 Jun 2013 11:05:13 -0700 (PDT)
Received: by 10.58.47.8 with HTTP; Wed, 19 Jun 2013 11:05:13 -0700 (PDT)
In-Reply-To: <CABkgnnUcFQEH5xL50qROdxmSvNotOh2rSoxoHp=3ASrKUm5O4A@mail.gmail.com>
References: <CABP7Rbe9GEkRvoU6yYpiNjrShc32PeoB64fNaTrP6M4Uco-xRw@mail.gmail.com> <CAOdDvNr_a3y7Aq8=Q77JYx=iJGwaK==wQWj5JVi9mMdqG5KJug@mail.gmail.com> <alpine.LRH.2.01.1306190738140.31315@egate.xpasc.com> <CA+pLO_jVAdz3XNsfUSW4L0a_dB4YSnaNA+G8QA9h0rS=b74s5w@mail.gmail.com> <CAP+FsNf7mZC3KMD5qYAPA8rAE+Q6fYM_xAEUtxEZQ0jSLGtAMw@mail.gmail.com> <CA+pLO_j-4X+NCO7LhmPR4iuUNMRyTuq-EezEs_iPmeuJ7JakBQ@mail.gmail.com> <CABkgnnXpAHVTHRALduELri5HqF77Jp6P7TGF-Uo2rhg+ysftJA@mail.gmail.com> <CAA4WUYgKJwhQGsyUyJzcaqy4C-iETsvqb9yPNax5JSixCNCu=A@mail.gmail.com> <CABkgnnUcFQEH5xL50qROdxmSvNotOh2rSoxoHp=3ASrKUm5O4A@mail.gmail.com>
Date: Wed, 19 Jun 2013 11:05:13 -0700
Message-ID: <CABP7RbdzogVE-JhLVMszEX8rDw8APHJkSDPs+ORQCbjQ13Qoaw@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ChanWilliam(陈智昌)" <willchan@chromium.org>, ietf-http-wg@w3.org, Roberto Peon <grmocg@gmail.com>, Jeff Pinner <jpinner@twitter.com>
Content-Type: multipart/alternative; boundary="bcaec547c84fd2940004df85ab0a"
Received-SPF: pass client-ip=209.85.212.47; envelope-from=jasnell@gmail.com; helo=mail-vb0-f47.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.678, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UpMlH-0007jU-1S ba80215dd0ed38a3e0e2bfd8c0c3bffb
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
Archived-At: <http://www.w3.org/mid/CABP7RbdzogVE-JhLVMszEX8rDw8APHJkSDPs+ORQCbjQ13Qoaw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18291
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

For now, in the implementation draft, can we keep this focused on whether
or not to rename this one existing error code rather than expand into too
much philosophical debate about error codes in general? We can refine the
error code mechanism if necessary later on.
On Jun 19, 2013 11:00 AM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> On 19 June 2013 10:28, William Chan (陈智昌) <willchan@chromium.org> wrote:
> > Actionable difference: it tells you what part of your stack to debug.
> > PROTOCOL_ERROR is terrible :( Everytime we generate a PROTOCOL_ERROR, we
> > have felt we wanted to add a debug string (that opaque byte sequence we
> > discussed earlier) so we could figure out what was wrong.
>
> I thought that was the reason you wanted to put the opaque stuff in the
> body.
>
> The reason I'm pushing back is that it is possible to spend error code
> bits on any amount of subdivision of the PROTOCOL_ERROR space.  Do you
> want one for the case where someone didn't echo the bytes of a PING?
> Or when they decide to send something else rather than continuing a
> HEADERS block?  Or any of the many current and future
> your-implementation-is-broken cases?  Ultimately, this just leads to a
> blowout in error codes, to no good end.
>
>

v2.23.0 | Report a Bug | By Email