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

Willy Tarreau <w@1wt.eu> Sun, 24 July 2011 18:33 UTC

Return-Path: <w@1wt.eu>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E02A21F89C1; Sun, 24 Jul 2011 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.941
X-Spam-Level:
X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[AWL=-3.198, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
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 DOLzd0tJo1M6; Sun, 24 Jul 2011 11:33:48 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 1410C21F889A; Sun, 24 Jul 2011 11:33:47 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6OIXh7n027121; Sun, 24 Jul 2011 20:33:43 +0200
Date: Sun, 24 Jul 2011 20:33:43 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Message-ID: <20110724183343.GY22405@1wt.eu>
References: <CALiegf=pYzybvc7WB2QfPg6FKrhLxgzHuP-DpuuMfZYJV6Z7FQ@mail.gmail.com> <CAP992=FJymFPKcPVWrF-LkcEtNUz=Kt9L_ex+kLtjiGjL1T46w@mail.gmail.com> <4E28A51F.4020704@callenish.com> <CALiegf=4K2oWfmZjGMD7J_jyaDtS3i+Mu7R0Wh75Rr+MrQCjtw@mail.gmail.com> <20110722054345.GE18126@1wt.eu> <9031.1311500145.687172@puncture> <20110724105223.GL22405@1wt.eu> <CALiegfkTVg2=k4d8rxmpqXmaRUihRmhtgfF4QRUTAKic7gBk5w@mail.gmail.com> <20110724121147.GR22405@1wt.eu> <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=GDDKdXOXgz3oognh6=qRDKFUSrRfLOtOoUucAxr4p3w@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: Server-Initiated HTTP <hybi@ietf.org>, IETF-Discussion <ietf@ietf.org>
Subject: Re: [hybi] Last Call: <draft-ietf-hybi-thewebsocketprotocol-10.txt> (The WebSocket protocol) to Proposed Standard
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 24 Jul 2011 18:33:49 -0000

On Sun, Jul 24, 2011 at 08:25:05PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/24 Willy Tarreau <w@1wt.eu>eu>:
> >> > Making an additional DNS request and a connection come with a cost.
> >>
> >> http://tools.ietf.org/html/draft-ibc-websocket-dns-srv-02#section-5.2
> >
> > You still need the DNS request : the client does an A/AAAA request for
> > the HTTP host, then if you ask it to use an SRV record for the WS connection,
> > it must perform that request too, even if it's to conclude that it can reuse
> > the idle connection.
> 
> Ok, but I don't consider a xtra DNS query to be so hard.

I had to perform sites analysis for a customer a few months ago. Many
web pages nowadays have between 100 and 200 objects to fetch, spread
over up to 25-30 host names. If you take even only 100ms for each of
them, you're at 3 additional seconds to display the page. Granted those
requests are not WS and only HTTP, but as I said, SRV for WS won't work
before it works with HTTP, at least due to proxies.

But those 3 extra seconds will always be considered a good reason not
to make SRV mandatory for HTTP. The web is degrading very quickly due
to poor practices, and we should be careful not to suggest to make it
even worse.

Regards,
Willy