IETF Logo Mail Archive

Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Tue, 26 July 2011 01:01 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C784921F8B80 for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.076
X-Spam-Level:
X-Spam-Status: No, score=-0.076 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
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 yqO56ZbJ5Kxg for <ietf@ietfa.amsl.com>; Mon, 25 Jul 2011 18:01:25 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id EF0A821F8B81 for <ietf@ietf.org>; Mon, 25 Jul 2011 18:01:24 -0700 (PDT)
Received: (qmail 98401 invoked from network); 26 Jul 2011 01:20:49 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 26 Jul 2011 01:20:49 -0000
Message-ID: <4E2E11C3.2000603@necom830.hpcl.titech.ac.jp>
Date: Tue, 26 Jul 2011 10:00:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
References: <20110721163910.GA16854@1wt.eu> <CAP992=FrX5VxP2o0JLNoJs8nXXba7wbZ6RN9wBUYC0ZSN_wbAg@mail.gmail.com> <9031.1311270000.588511@puncture> <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <B2C17B21-EA8A-4698-8C41-F55A9AA140D4@gbiv.com> <CALiegfkshhJVUHzTD1Kka5+RjGwZ5CS2J=Qk92jfSBg6Z0VfOQ@mail.gmail.com> <C9CD680E-8D68-4380-A76F-70F41F30F877@gbiv.com> <CALiegfkFnKjP09Vijo3c_DFYn4=UZm9M-4mVuZUyBk8rzwmDCw@mail.gmail.com> <20110724191641.GC22405@1wt.eu> <644A437E-BB0D-45E9-B6C3-5EF66A811986@virtualized.org> <20110725045821.GN22405@1wt.eu>
In-Reply-To: <20110725045821.GN22405@1wt.eu>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jul 2011 01:01:25 -0000

Willy Tarreau wrote:

> What are you saying ? Your browser embeds the resolved as a library, so when
> I'm saying that "the browser has to retry", I mean the resolver part of the
> browser has to retry.

You should mean that the browser can control behavior of the
resolver.

If the resolver in the browser retries within a hundred ms:

> So yes, it can take several seconds to just resolve a host and then
> only a few hundreds of ms to retrieve
> the objects. I've observed it.

won't happen.

						Masataka Ohta

v2.23.0 | Report a Bug | By Email