IETF Logo Mail Archive

Re: [hybi] deflate-stream and masking

John Tamplin <jat@google.com> Wed, 20 July 2011 20:45 UTC

Return-Path: <jat@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 4288C21F862F for <hybi@ietfa.amsl.com>; Wed, 20 Jul 2011 13:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.926
X-Spam-Level:
X-Spam-Status: No, score=-105.926 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb5BvWueGJ3o for <hybi@ietfa.amsl.com>; Wed, 20 Jul 2011 13:44:59 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 49F9D21F85F3 for <hybi@ietf.org>; Wed, 20 Jul 2011 13:44:59 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p6KKiwPR024786 for <hybi@ietf.org>; Wed, 20 Jul 2011 13:44:58 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311194698; bh=IaSDoxOewDMSKM6w85AuL6zpiDU=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=dFCqvxBoIRZmbekw4FvcbzDk12loaNCcgnZ7w7O8Sd+2Lt9SnKlcCa7ZgpwthsPBH rIwQP/2neCaurMRGIOvEQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=eZo31w+8tCAL9+dVdd50Mnj/Or+je4oQXiTA+Swe0WagLXxtr+CGN7XMp9PX/VbJa mdApZHT4H97uivlNEHxmA==
Received: from gwj17 (gwj17.prod.google.com [10.200.10.17]) by wpaz13.hot.corp.google.com with ESMTP id p6KKi2t5019254 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Wed, 20 Jul 2011 13:44:57 -0700
Received: by gwj17 with SMTP id 17so675974gwj.38 for <hybi@ietf.org>; Wed, 20 Jul 2011 13:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lDFM72gT5q6sc3NwvmHriQBgcL25VAVp0OwkR31xN5U=; b=Hvv2baMIdHyFla11BtUqGUuH6tZ3Q8CHYYQgZlwGYujFuIp2JPK+ujd0qmSRO4Icm/ 9Kx8ufUhm1Xn96ia8LYQ==
Received: by 10.150.116.12 with SMTP id o12mr7375212ybc.2.1311194697132; Wed, 20 Jul 2011 13:44:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Wed, 20 Jul 2011 13:44:36 -0700 (PDT)
In-Reply-To: <CAP992=F4hCgsm_yg6kkSK_PqVehLm=Xam3zB8oy6JBDTk9ub9A@mail.gmail.com>
References: <BANLkTi=UVMAd1nER6mRBe7zoD29CSbCkGA@mail.gmail.com> <CAH_y2NFMdr1ZU2dfy9mCRepZc2R_hnzg0oa3kYPKhWY-FX_8Og@mail.gmail.com> <CAE8AN_V-P2L0mVwjPQYxAypJ67=QWKAhWnDqrM_XmDQXjJbEHA@mail.gmail.com> <CAP992=HmZM9H2i+rFLVNrJVzfQT2qSPzWRm4gQXc2wTQ8fdBTA@mail.gmail.com> <00b801cc470a$d2d5e520$7881af60$@noemax.com> <CAP992=Gvz7CT=fZSX=t_7J3YAGF7kKsA9a6M0UQJP3HXxMBANQ@mail.gmail.com> <1311190993.1862.135.camel@ds9> <4E273125.8070503@stpeter.im> <CA566BAEAD6B3F4E8B5C5C4F61710C114038FBE3@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com> <1311192266.1862.138.camel@ds9> <CAP992=F4hCgsm_yg6kkSK_PqVehLm=Xam3zB8oy6JBDTk9ub9A@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Wed, 20 Jul 2011 16:44:36 -0400
Message-ID: <CABLsOLAEE02pNHAUBBXzJKqCeQU-ozbesOpa9BtEgKXBQWceaw@mail.gmail.com>
To: David Endicott <dendicott@gmail.com>
Content-Type: multipart/alternative; boundary=000e0cd32b94276b3004a8864eec
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>, Patrick McManus <pmcmanus@mozilla.com>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>
Subject: Re: [hybi] deflate-stream and masking
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, 20 Jul 2011 20:45:00 -0000

On Wed, Jul 20, 2011 at 4:36 PM, David Endicott <dendicott@gmail.com> wrote:
>
> I've always understood WS as a protocol that defines how content is
> exchanged asynchronously between "web" peers.   It is a framing mechanism
> for TCP.   It is not an application layer (it doesn't define "verbs", like
> GET, POST, HEAD, etc.).    Transport layers should be content agnostic.
> Compression is a function of that which uses the transport layer (ie.
> application layer).    But, I've said this before, and there is no reason
> to belabor the point.
>

The point is that practically all content which will be going over
WebSockets will benefit from compression (see my experiments documented here
a year and a half ago, which included clients sending binary data).  Without
compression built into the spec, developers may be forced into a position of
continuing to use XHR hacks because the lack of compression makes WS slower
(for example, Google Instant search).

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.1.22 | Report a Bug | By Email