IETF Logo Mail Archive

Re: [hybi] workability (or otherwise) of HTTP upgrade

John Tamplin <jat@google.com> Fri, 10 December 2010 00:47 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 27DFF3A6BEC for <hybi@core3.amsl.com>; Thu, 9 Dec 2010 16:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.139
X-Spam-Level:
X-Spam-Status: No, score=-105.139 tagged_above=-999 required=5 tests=[AWL=0.837, 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 uz6inOpWdmrS for <hybi@core3.amsl.com>; Thu, 9 Dec 2010 16:47:08 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 8692D3A6BE7 for <hybi@ietf.org>; Thu, 9 Dec 2010 16:47:07 -0800 (PST)
Received: from hpaq5.eem.corp.google.com (hpaq5.eem.corp.google.com [172.25.149.5]) by smtp-out.google.com with ESMTP id oBA0malU013070 for <hybi@ietf.org>; Thu, 9 Dec 2010 16:48:37 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1291942117; bh=UjXGfuw2k9y16LFMKbG4+7m3mpI=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=JhI5YZmUvODfH1b0GmDUvtHB1Y2rDT14yhBZEiQO9jAg5J0ztFTLwwckASJVFBKb1 nGXe1v3nE66aQHO/tLpGg==
Received: from yxd5 (yxd5.prod.google.com [10.190.1.197]) by hpaq5.eem.corp.google.com with ESMTP id oBA0lpok021870 for <hybi@ietf.org>; Thu, 9 Dec 2010 16:48:35 -0800
Received: by yxd5 with SMTP id 5so1896138yxd.20 for <hybi@ietf.org>; Thu, 09 Dec 2010 16:48:35 -0800 (PST)
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=x3ViLOW2lAkzsEUioyaXW5csZgyhenPK+u50SpNFpO0=; b=vuY+N6nxpEkLR33Hl1iA/OdYgnfsCo1X+eBWh8G7a7x6YeoNQNEma8Vh3wSVFAvyHf TSMNNy3sy3owXwVw8lCQ==
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=bWrwxeJHiO/RLShYzhUuMeyNb68CpKWQCgUY3XPRzCmPcTwin8cL240RUPx0kZXdKl jTmDBair90rUihKVVyTA==
Received: by 10.150.91.18 with SMTP id o18mr435080ybb.92.1291942114881; Thu, 09 Dec 2010 16:48:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.137.17 with HTTP; Thu, 9 Dec 2010 16:48:14 -0800 (PST)
In-Reply-To: <op.vng1ixmaidj3kv@dhcp-190.linkoping.osa>
References: <BB947F6D-15AA-455D-B830-5E12C80C1ACD@mnot.net> <81870DB1-B177-4253-8233-52C4168BE99D@apple.com> <F4D1B715-3606-4E9A-BFB2-8B7BC11BE331@mnot.net> <57D4B885-B1D8-482F-8747-6460C0FFF166@apple.com> <37A00E8D-B55C-49AD-A85C-A299C80FFF17@mnot.net> <4F2580A7-79C2-4B0A-BCE5-7FB6D9AA0ED7@apple.com> <BB31C4AB95A70042A256109D461991260583956C@XCH117CNC.rim.net> <EA41A6C7-971C-4EC8-AA6F-96363B7FDC4C@gmail.com> <73E53F19-E0E7-4ADB-B765-ABAF0B4A6736@mnot.net> <r2f0g6d7bj770kg0db5ptr027ninmckns8@hive.bjoern.hoehrmann.de> <20C2FBB9-901F-4235-AF23-EC8262585905@mnot.net> <1291905941.2315.2113.camel@ds9.ducksong.com> <4D011146.3080906@caucho.com> <AANLkTi=CKU8H5A2f7rSGZ9h5mrp=NZW0yLB9O6=MDW5i@mail.gmail.com> <AANLkTimg774w-JVExm4YQJzuBv3gaJZOLMo5OymDsMiE@mail.gmail.com> <op.vng1ixmaidj3kv@dhcp-190.linkoping.osa>
From: John Tamplin <jat@google.com>
Date: Thu, 09 Dec 2010 19:48:14 -0500
Message-ID: <AANLkTi=Ow=hGxwuOdMBtfmm2mBnYHK3d5TLRMkrpK_kd@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Content-Type: multipart/alternative; boundary="000e0cd406dcd3f2a1049703b609"
X-System-Of-Record: true
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] workability (or otherwise) of HTTP upgrade
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: Fri, 10 Dec 2010 00:47:11 -0000

On Thu, Dec 9, 2010 at 7:12 PM, Simon Pieters <simonp@opera.com> wrote:

> But what is the use case for cookies in WebSockets? (If it has been
> discussed before then I have missed it and would appreciate pointers.)
>

Simply that applications split between HTTP and WebSockets are likely to
want to share that data.  If you don't include cookies, then you force every
app to reinvent the wheel of how to transfer their session ID/etc.

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

v2.23.0 | Report a Bug | By Email