[hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_

Takeshi Yoshino <tyoshino@google.com> Wed, 09 October 2013 08:07 UTC

Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEBE321E80F5 for <hybi@ietfa.amsl.com>; Wed, 9 Oct 2013 01:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 UnU+gxh2g3RW for <hybi@ietfa.amsl.com>; Wed, 9 Oct 2013 01:07:01 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB8321E80E2 for <hybi@ietf.org>; Wed, 9 Oct 2013 01:06:55 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id y10so467331wgg.10 for <hybi@ietf.org>; Wed, 09 Oct 2013 01:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=v9YYl6NnTI/7ROeNM4r9lHguN2LbWHGHRYSwFRhpJiE=; b=bpNTJeAUr8pt0f16UO126nkIkc6L8yyJHPiRKptRzLsE56ptsBoZsNsd0kvUKVk4FQ mFRkDFlbLFFspvqIhdhtEZfZtUwrvLYVCh7A8PTfR3SlOtYl6C5FPXDmqXeBIHZk16H8 ON5dh66vCKGyeMovX3ciPo96wamfYKO/TlN0jBk8AeNn/zsOIK8qH7zB2BhQ45HFrt/z IXbMucbNirstZMFLkS8jghnfK4VNNOkpTEN1PNHp+33dj5W2ltu1+Kk+IWlWILWlhMyK SPApNW5+FeivcC1SJvwGFT06mWQgd7RuvgJXTAx3nqEKvnqiOmtyGlR/3B9ywF6/zf/+ XEPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=v9YYl6NnTI/7ROeNM4r9lHguN2LbWHGHRYSwFRhpJiE=; b=MdZqtMCUSVFS38Bs39dW3zSrIKCdTjITLOGW0T1SXluALuVfiNqZntB2uqsFxfwJkH Kr+/nCZLO7ostIuxWzoO1bZHPPvxa74MW4yMg7qeZnQNmK9puTs0aurpVxwBlJUTBR7i 1FJABcjJv7o/PW7Kq9rz1Q523xE4l6Bwpgcd9F/fbwRNUUjkuQKSGTa/gR8vg118VQby 39yKSdQrNW4aW79Dbi1npEMA0A/SBcX7jeNNXYf30p41SYtwHJL8y+p8+v8kId0LVxTK VCo8rFXT/w0/EgAhjzwsUFG8+BT1a+kD2U+qNyVd08/CrB9nNn9MNk5flvkBpDpl12x/ gSmQ==
X-Gm-Message-State: ALoCoQmNGHqMi4Amq4tqUijpUNGJurg0baUOSlbzKpJ+UiN9BPfygL3ZZGAvbC2/9ul6Vg6dwhmlfXzoB8fvDLwPOk6QsTqqPFd/MGeOGvsgfuKai5flNSMpDrYg4HsYryu14l0a8dLq/JCROeJ2vXEjMnVT3KR5Bl39VnCdI/HcR2gbDKzm2r4lUp0GWa+FsUyDDLoYCnct
X-Received: by 10.180.89.98 with SMTP id bn2mr1535717wib.42.1381306015089; Wed, 09 Oct 2013 01:06:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 01:06:35 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 09 Oct 2013 17:06:35 +0900
Message-ID: <CAH9hSJant3VBw0FBM69V9wPvi3WmJLikZdX4ySELy+CShgoOKA@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary="f46d04447fbb5b23df04e84a5edb"
Subject: [hybi] [permessage-deflate] Renaming s2c_ and c2s_ prefix to server_ and client_
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2013 08:07:02 -0000

(Splitting into an independent thread)

Joakim suggested that we should rename them.
http://www.ietf.org/mail-archive/web/hybi/current/msg10201.html
 > Since all websocket communications are initiated by client to server
 > these should just be s/s2c_/server_/g and s/c2s_/client_/g

Initially, I chose these prefixes to make it easy to understand that
they're attributes for each direction by including source and destination
explicitly. But server_ and client_ are not so confusing, too. As these
parameters are request about the peer's output, everyone should understand
X_no_context_takeover and X_max_window_bits as parameters instructing
compressor of X.

If we do this, we should do this right now. I don't have strong opinion
about this change. If there's no objection, I'll take it.