IETF Logo Mail Archive

Re: [hybi] DNS SRV for WebSocket

Greg Wilkins <gregw@intalio.com> Mon, 28 March 2011 20:38 UTC

Return-Path: <gregw@intalio.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 D7F0A3A6A2B for <hybi@core3.amsl.com>; Mon, 28 Mar 2011 13:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 fUWtYwq8rXVK for <hybi@core3.amsl.com>; Mon, 28 Mar 2011 13:38:09 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 16B733A6902 for <hybi@ietf.org>; Mon, 28 Mar 2011 13:38:09 -0700 (PDT)
Received: by vxg33 with SMTP id 33so3078839vxg.31 for <hybi@ietf.org>; Mon, 28 Mar 2011 13:39:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.0.4 with SMTP id 4mr2932569vda.104.1301344786491; Mon, 28 Mar 2011 13:39:46 -0700 (PDT)
Received: by 10.52.155.71 with HTTP; Mon, 28 Mar 2011 13:39:46 -0700 (PDT)
In-Reply-To: <BANLkTi=jPJ+guXuz=tr29kbVj5CxjSfXMA@mail.gmail.com>
References: <BANLkTi=G6bc=FquLM8agKWojmDkD9FohxA@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F04027B925A@SISPE7MB1.commscope.com> <BANLkTi=jPJ+guXuz=tr29kbVj5CxjSfXMA@mail.gmail.com>
Date: Tue, 29 Mar 2011 07:39:46 +1100
Message-ID: <AANLkTi=px=ainKobe-oUjmkgB2AE9n==VyvWcgr6cv0z@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "Thomson, Martin" <Martin.Thomson@commscope.com>, Hybi <hybi@ietf.org>
Subject: Re: [hybi] DNS SRV for WebSocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Mon, 28 Mar 2011 20:38:10 -0000

On 28 March 2011 19:34, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> Also, I've explained that SRV is not just for "provide name-based
> discovery for a service". SRV provides *Real* load-balancing and
> failover. This doesn't exist in HTTP (in which just a hack is used: a
> DNS A record with different IP's).

So the problem using SRV for ws is that ws starts with a HTTP connection,
which may be existing and may be used for other HTTP requests if the
handshake fails.

So there is not much we can do to tell clients that they should use
SRV when creating the HTTP connection.

So why doesn't HTTP use it?

cheers

v2.23.0 | Report a Bug | By Email