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

Willy Tarreau <w@1wt.eu> Wed, 27 July 2011 15:37 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 6D52C21F899F; Wed, 27 Jul 2011 08:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[AWL=-2.462, 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 6Oidh-MKeLdq; Wed, 27 Jul 2011 08:37:34 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7C721F891F; Wed, 27 Jul 2011 08:37:32 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RFbQ83007587; Wed, 27 Jul 2011 17:37:26 +0200
Date: Wed, 27 Jul 2011 17:37:26 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Message-ID: <20110727153726.GA7579@1wt.eu>
References: <20110724204236.GG22405@1wt.eu> <CALiegfkgukeaiMR-Yc15qUJYCB-KPcoNoX4G6NrN4+DOiDS+tw@mail.gmail.com> <20110726192850.GB3692@1wt.eu> <CALiegfndubt3xgRLFWUikhizsvX60p4+b0DcouX0_m5B8vestg@mail.gmail.com> <20110727101757.GA6586@1wt.eu> <CALiegfmMO2Es6P=qy4m=XULVQE9bDp7S0LYXG_9n4Lk9yirGXQ@mail.gmail.com> <20110727124545.GA6931@1wt.eu> <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@mail.gmail.com> <20110727140302.GB7225@1wt.eu> <CALiegfmWWL2sxB=4=kD-YmE30rsS3_-DGqePCohv_hv2QQfJUw@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: <CALiegfmWWL2sxB=4=kD-YmE30rsS3_-DGqePCohv_hv2QQfJUw@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: Wed, 27 Jul 2011 15:37:34 -0000

On Wed, Jul 27, 2011 at 05:19:30PM +0200, Iñaki Baz Castillo wrote:
> Well, I understand (and agree) most of your text, but I still think
> that the URI resolution mechanism is something transparent for an
> end-user. This is not like having FlashPlayer for showing annoying and
> dancing menus in a web page XD. End-users ask for FlashPlayer (and
> Android 2.3 has included it for example) but end-users won't ask for
> "SRV procedures".

They won't "ask for", but when some sites pretend "we work better with",
then they'll ask for the techno to use the site better. It's similar to
the HTTP/1.0 or 1.1, keep-alive and pipelining that you can enable in
your browser. Most users won't play with it, still that's pretty
configurable. Similarly end users can decide to enable/disable IPv6 or
IDN.

> I would translate your arguments to "web developers", those who want
> to provide scalable systems and for which having some kind of QoS
> mechanisms (specially for mobile devices) is a great advantage. Of
> course, if this happens then end-users would be happier :)

I think you got it :-)

Willy