Re: [hybi] WebSocket & Nagle
Ian Fette (イアンフェッティ) <ifette@google.com> Fri, 18 March 2011 18:53 UTC
Return-Path: <ifette@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 CBE923A6999 for <hybi@core3.amsl.com>; Fri, 18 Mar 2011 11:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.696
X-Spam-Level:
X-Spam-Status: No, score=-105.696 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 kCfk0GeTTXy7 for <hybi@core3.amsl.com>; Fri, 18 Mar 2011 11:53:38 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id DBBE53A695C for <hybi@ietf.org>; Fri, 18 Mar 2011 11:53:37 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id p2IIt6K1024861 for <hybi@ietf.org>; Fri, 18 Mar 2011 11:55:06 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1300474507; bh=EFt7vbnQDL43XeA6t7ybUtXnN2w=; h=MIME-Version:Reply-To:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type; b=JwFEgwdytgKXgdlnU5kaGI4G8d2GGv+OZ3Hdq4ucUzCBKowZntUZwIaSagyztfAs4 QCfNQi0EqFduMjHJv7FnQ==
Received: from iyi12 (iyi12.prod.google.com [10.241.51.12]) by hpaq11.eem.corp.google.com with ESMTP id p2IIso3G017308 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Fri, 18 Mar 2011 11:55:05 -0700
Received: by iyi12 with SMTP id 12so6266981iyi.17 for <hybi@ietf.org>; Fri, 18 Mar 2011 11:55:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=vjUYarf9y26eAakAZUXcocOjxselTeu+NeaaOu5WyrU=; b=RrPCSGwECYsVbacfSsUqMGAT0eVDT1xMjEMtVnb2M9Jk7gx0/b1/+sC6z7t4tV23GU KQF+oRd0vFTx+cu03WMw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=wpBgxuWfOVLvWSMT7d+oedXV7Hix0wkDYyHrwjrW2R6fIy9IGp0sWW0PqXQVlEO9Kt eXGPOUff/3PcjNegAVIQ==
MIME-Version: 1.0
Received: by 10.43.55.83 with SMTP id vx19mr2293567icb.24.1300474504658; Fri, 18 Mar 2011 11:55:04 -0700 (PDT)
Received: by 10.231.34.131 with HTTP; Fri, 18 Mar 2011 11:55:04 -0700 (PDT)
In-Reply-To: <000501cbe59a$62701cf0$275056d0$@net>
References: <000501cbe59a$62701cf0$275056d0$@net>
Date: Fri, 18 Mar 2011 11:55:04 -0700
Message-ID: <AANLkTimktGQp_5uc8ft51AbtRqw4FqaK5eNM9b7zrWL2@mail.gmail.com>
From: "Ian Fette (イアンフェッティ)" <ifette@google.com>
To: Greg Longtin <Greg@championent.net>
Content-Type: multipart/alternative; boundary="bcaec517a9aee3c0a1049ec6501a"
X-System-Of-Record: true
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] WebSocket & Nagle
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ifette@google.com
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, 18 Mar 2011 18:53:38 -0000
in Chrome, we disable nagle fwiw. -ian On Fri, Mar 18, 2011 at 11:29 AM, Greg Longtin <Greg@championent.net> wrote: > To all, > > I have been working with WebSocket, based on it being a browser based > socket > interface for intranet use. > > I've created a Windows server, and have been testing with the MSFT 05 and > 06 > Silverlight prototypes and Pat McManus' WS 06 Minefield build (thank you.) > > I believe all three implementations allow the use of the Nagle algorithm > for > sending client packets. On my system, this intermittently introduces a 200 > mS delay, along with the combining of packets. IMHO, for many > applications, > that amount of delay isn't acceptable. > > I'm not an Internet network type, so I'm not familiar with implications at > that level. > > From my perspective, it would be best if either Nagle was disabled for > WebSocket packets, or the browser script API would allow one to do so. I > realize that option is outside of hybi spec. > > Thanks, > > Greg > > _______________________________________________ > hybi mailing list > hybi@ietf.org > https://www.ietf.org/mailman/listinfo/hybi >
- [hybi] WebSocket & Nagle Greg Longtin
- Re: [hybi] WebSocket & Nagle Ian Fette (イアンフェッティ)
- Re: [hybi] WebSocket & Nagle Andy Green
- Re: [hybi] WebSocket & Nagle Gabriel Montenegro
- Re: [hybi] WebSocket & Nagle Pat McManus @Mozilla