[hybi] New Chrome WebSocket implementation: testers wanted
Adam Rice <ricea@google.com> Tue, 15 April 2014 06:11 UTC
Return-Path: <ricea@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1C11A04B6 for <hybi@ietfa.amsl.com>; Mon, 14 Apr 2014 23:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.65
X-Spam-Level: *
X-Spam-Status: No, score=1.65 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xfDt_R45OALg for <hybi@ietfa.amsl.com>; Mon, 14 Apr 2014 23:11:52 -0700 (PDT)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id E0AF91A008B for <hybi@ietf.org>; Mon, 14 Apr 2014 23:11:51 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id i7so10433740oag.9 for <hybi@ietf.org>; Mon, 14 Apr 2014 23:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=mUUOeOwWm+juQtlsq2gG6UT/eylKI94bSwS+Jdsisoo=; b=XDutaMZGvtdOo293e9bgNTSY/A3+TQx6EQcABIa8cTIwYI/F1NtXDcyZJ4Pc+prGSf D0qr2q/GPK4RPIT+xWy1re1GtbOgM0ohhieuWltBhjo9DhRoEN36biznXxgHpVe9iRe/ wLkoG2pCziULBFRtf0qnWnRJofQk58yu2gcIWAGA43drKXObN6+7oMFQ5rDi9r2UREU9 X8ccDGZzpd9TmScF7mWDOzS0qGRWe9k7VWtY34ETOQFtP8jj7b67HCyrHbYk46wCgTV0 zxBLaEtQUfxHxwquMi7xSHmoQowlhG5APB1rqpyvgNau12RHMCTjesD8/qOXG1/0afFd zPtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=mUUOeOwWm+juQtlsq2gG6UT/eylKI94bSwS+Jdsisoo=; b=KyyEZInm2YHLNqo0deJ0yPceJDU28SggEu5HDAwsIYhCiwGvMNT54+BuQsJB6U5oyJ SgWxJhHdXmPIHWjg3EPTZoZCUcClG3eoqs+ytgiUZuz/2cLMPClQxCv9AHRtxy/iwRCb 0OtGRRSaCmgbOtWUuCUMgwJl5Rwh8z2JUHgcOwjXD5EcRRg2FhDgr7YmnDpzhm5grNWy Ibegr9RLXzwndYOiy9bJg3lJGUt3w8XukKA+vlNK/I9hX90TUQPbjZo1Y3s2YDkEfADZ OpyV89ZGEXxkyL2gJ7/za7LlQwxxqVyM9+ZxTfXC8BZz1M0CIymd+wc6yDs4WLa78DPe XHvA==
X-Gm-Message-State: ALoCoQk8k3XvVSvA8MTox9knJ3PE/tQ66pkY9xUfIyEOZxrNGcnuzgv2xaN8mtg8cF+5h6azQU6Anj5iKKEpBbhtJuFFMUFuayU1nT8fli0PBH+R4QA9TXJivjJVZtuzzYKqC3yPlj5qqUy6Kw1Zg8a7gRrCG0lDQpgGywZlBD2nactZjGw5qclUIONGZ2bx6rhAoUNz5MNg
MIME-Version: 1.0
X-Received: by 10.182.225.163 with SMTP id rl3mr12593obc.79.1397542309066; Mon, 14 Apr 2014 23:11:49 -0700 (PDT)
Received: by 10.182.76.167 with HTTP; Mon, 14 Apr 2014 23:11:49 -0700 (PDT)
Date: Tue, 15 Apr 2014 15:11:49 +0900
Message-ID: <CAHixhFrA2FH6JOOFkd9sjBtgvBKEO6CZ9K9T-NdKf8PvXTiG2A@mail.gmail.com>
From: Adam Rice <ricea@google.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c2e672e41f4604f70eac93"
Archived-At: http://mailarchive.ietf.org/arch/msg/hybi/dW4qcsyuBOA9UdxgslVVa69yBeo
Subject: [hybi] New Chrome WebSocket implementation: testers wanted
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 15 Apr 2014 06:11:53 -0000
The latest dev build of Chrome includes a new WebSocket implementation behind an experimental flag. If you have version 36.0.1933.0 or greater, you can enable it using the "Enable experimental Web Platform features" flag in about:flags. An easy way to distinguish the different implementations is that the stable implementation does not set the "Accept-Language:" header, whereas the new implementation does. You can examine the headers by opening the Network panel in "Developer Tools" before creating the WebSocket connection. A known issue with the new implementation is that RFC6455 connection throttling is not implemented yet. This will be done Real Soon Now. We are interested in hearing about any compatibility problems you might encounter, either server side or in client libraries. Feedback welcome. Adam Rice
- [hybi] New Chrome WebSocket implementation: teste… Adam Rice
- Re: [hybi] New Chrome WebSocket implementation: t… Dario Crivelli
- Re: [hybi] New Chrome WebSocket implementation: t… Adam Rice
- Re: [hybi] New Chrome WebSocket implementation: t… Dario Crivelli
- Re: [hybi] New Chrome WebSocket implementation: t… Adam Rice