Re: [hybi] WebSocket handshake (HTTP and SSO)

John Tamplin <jat@google.com> Sat, 04 September 2010 12:37 UTC

Return-Path: <jat@google.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 949773A6834 for <hybi@core3.amsl.com>; Sat, 4 Sep 2010 05:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.878
X-Spam-Level:
X-Spam-Status: No, score=-105.878 tagged_above=-999 required=5 tests=[AWL=0.098, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5yipsqUekZJ8 for <hybi@core3.amsl.com>; Sat, 4 Sep 2010 05:37:34 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 9B1753A682D for <hybi@ietf.org>; Sat, 4 Sep 2010 05:37:34 -0700 (PDT)
Received: from hpaq7.eem.corp.google.com (hpaq7.eem.corp.google.com [172.25.149.7]) by smtp-out.google.com with ESMTP id o84Cc29U003258 for <hybi@ietf.org>; Sat, 4 Sep 2010 05:38:03 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1283603883; bh=FXKr66OSAirBOdvnrpzdIbReuO0=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=Tel3emyv23doJBBeGFdVrFFKw7FaoU3qc7rkTkqm/g0NNvlre3MUSMKWc+tMVDxhS oAxUYR4oYFP9OG7bMxwKA==
Received: from gwaa18 (gwaa18.prod.google.com [10.200.27.18]) by hpaq7.eem.corp.google.com with ESMTP id o84Cc1lB008556 for <hybi@ietf.org>; Sat, 4 Sep 2010 05:38:01 -0700
Received: by gwaa18 with SMTP id a18so1492083gwa.40 for <hybi@ietf.org>; Sat, 04 Sep 2010 05:38:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=mo1M3XFefJ05+//YqBA0U94jWh/tR3qPtJEQTm0P80w=; b=g2wIxeq6SMxEckOSnXrTOhwUhdjbRToAJgY2RTEsr1xrNdg+5W5ncZ8A/AL3MuL8MU JigsZO19MfZe0KpueNBA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=yvim+Q1T18JutuWdcU0h/myChcec6WtmH8gOSIBwsU7KZjio6mH+6g8T9iSFKHy88D YXamjI0OQkXUu90cDFaQ==
Received: by 10.151.132.9 with SMTP id j9mr367165ybn.403.1283603880730; Sat, 04 Sep 2010 05:38:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.143.19 with HTTP; Sat, 4 Sep 2010 05:31:32 -0700 (PDT)
In-Reply-To: <AANLkTi=pD1tXjL4QV5p0Jf2WmSiGJ_7aVOthNnW8WB3u@mail.gmail.com>
References: <AANLkTinxTLuDEiS=XuyVHG1W+aizKHWk2Z4=LLqEHvC4@mail.gmail.com> <AANLkTik5uJ4wxUV-gvRmAMBe=JjOa-2yaA7zpf+hznS_@mail.gmail.com> <AANLkTi=pD1tXjL4QV5p0Jf2WmSiGJ_7aVOthNnW8WB3u@mail.gmail.com>
From: John Tamplin <jat@google.com>
Date: Sat, 04 Sep 2010 08:31:32 -0400
Message-ID: <AANLkTim_KL_=swvKkwsp6nf_mgPymEhyVSnpfQzmhFEE@mail.gmail.com>
To: Benjamin Black <b@b3k.us>
Content-Type: multipart/alternative; boundary="001485ea3b3457f1ed048f6e51a2"
X-System-Of-Record: true
Cc: hybi@ietf.org
Subject: Re: [hybi] WebSocket handshake (HTTP and SSO)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Sep 2010 12:37:35 -0000

On Sat, Sep 4, 2010 at 2:12 AM, Benjamin Black <b@b3k.us> wrote:

> I actually removed a sentence saying approximately "I don't see how
> this matters to anyone but Google", but thought it too snarky.  Next
> time I'll know!
>

Perhaps it should matter to more people -- experience has shown that usage
and user happiness goes up when latency goes down.  Many tools exist solely
to help developers make their websites faster (Google only provides a few of
these), and much of the suggestions center around reducing startup latency.
 As Ian mentions, there are lots of ways to hide latency in other places,
but you really can't hide startup latency.

So perhaps what you mean is "I don't see how this matters to anyone but
those wanting more usage and happier users".

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