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 14:03 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 6EC3621F86C3; Wed, 27 Jul 2011 07:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.186
X-Spam-Level:
X-Spam-Status: No, score=-4.186 tagged_above=-999 required=5 tests=[AWL=-2.443, 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 a1Tm9iQy0g9f; Wed, 27 Jul 2011 07:03:08 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD2F21F86C2; Wed, 27 Jul 2011 07:03:07 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id p6RE32Ou007260; Wed, 27 Jul 2011 16:03:02 +0200
Date: Wed, 27 Jul 2011 16:03:02 +0200
From: Willy Tarreau <w@1wt.eu>
To: =?iso-8859-1?Q?I=F1aki?= Baz Castillo <ibc@aliax.net>
Message-ID: <20110727140302.GB7225@1wt.eu>
References: <20110724185949.GB22405@1wt.eu> <9031.1311538720.416128@puncture> <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CALiegf=YCCYuoVk1isPOwfB1z8mpSxbJmFHU5vEyQo7xOGH5RA@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 14:03:08 -0000

On Wed, Jul 27, 2011 at 03:45:38PM +0200, Iñaki Baz Castillo wrote:
> 2011/7/27 Willy Tarreau <w@1wt.eu>eu>:
> > Once again, the goal to make SRV adopted BY USERS is not to ensure that
> > it tries to cover all the server-side needs, but that it offers better
> > quality of service to USERS. That way USERS will massively adopt it and
> > server will one day be able to safely rely on it. Just like neither
> > Javascript nor cookies nor flash are mandatory, still all of them are
> > very common in practice and many service providers happily rely on them.
> 
> Thanks for your useful comments (as always in these threads). Let me
> just a question:
> 
> What do you mean with "USERS"? Do you mean home users in front of
> their web browsers? or webbrowser vendors?

Users in front of web browsers.

> I don't think home users (neither professional users) has nothing to
> decide here, they will not "resolve" the WS URI retrieved from a
> webpage.

I think you're wrong. Those are these users which ask for feature XXX or
YYY that they like because it brings them a better experience. If you can
find a real benefit for the end user, there will be an option in the browser
and some of them will enable it. It's just important to find how an end user
may benefit from making use of SRV tags when connecting to his favorite site
instead of using just CNAME or A/AAAA. Maybe being able to always connect to
less loaded servers would be appreciated, because some site maintainers will
start announcing new servers. Maybe there are solutions to provide better
geolocation using SRV than with A (ie: let the web browser decide which field
to use instead of relying on its resolver's IP address). Maybe it will be
possible for mobile users to automatically select a different port which is
not subject to annoying transparent proxies at their provider. I don't know.
You must think in terms of better experience which might be brought via
better quality of service. Surely a DNS record might provide information to
improve QoS based on the browser's decision.

> So we are talking about webbrowser vendors, right? and typically there
> are no more than.... 10?

Browsers implement what their users ask for. They don't want to add features
that are not desired and make experience worse or reduce reliability. But if
users ask for something, they'll certainly implement it.

Regards,
Willy