Re: [hybi] WebSocket: current status and next steps
Iñaki Baz Castillo <ibc@aliax.net> Fri, 08 July 2011 10:52 UTC
Return-Path: <ibc@aliax.net>
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 86C7121F864E for <hybi@ietfa.amsl.com>; Fri, 8 Jul 2011 03:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 DaQkRiK2dh8r for <hybi@ietfa.amsl.com>; Fri, 8 Jul 2011 03:52:35 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0A36621F8612 for <hybi@ietf.org>; Fri, 8 Jul 2011 03:52:34 -0700 (PDT)
Received: by qyk9 with SMTP id 9so254471qyk.10 for <hybi@ietf.org>; Fri, 08 Jul 2011 03:52:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.137.19 with SMTP id u19mr1373253qct.173.1310122354061; Fri, 08 Jul 2011 03:52:34 -0700 (PDT)
Received: by 10.229.240.15 with HTTP; Fri, 8 Jul 2011 03:52:33 -0700 (PDT)
In-Reply-To: <CAKmKYaCumLtwt7M_PjkeBaOAGM=gX9v2GwWvzwseKT94xY9=9A@mail.gmail.com>
References: <4E16C0E5.40106@ericsson.com> <CAKmKYaCumLtwt7M_PjkeBaOAGM=gX9v2GwWvzwseKT94xY9=9A@mail.gmail.com>
Date: Fri, 08 Jul 2011 12:52:33 +0200
Message-ID: <CALiegfk7hTo7wBzXC=kEbNYZA5ce60Uqq38f+ORU9XAxxtDuSg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Dirkjan Ochtman <dirkjan@ochtman.nl>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WebSocket: current status and next steps
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: Fri, 08 Jul 2011 10:52:35 -0000
2011/7/8 Dirkjan Ochtman <dirkjan@ochtman.nl>: > As for DNS SRV, I briefly looked it over and think it would certainly > be nice to specify. I just wonder if it wouldn't make more sense to > put it inside the WebSocket Protocol spec, given the mandatory > machinations required from WebSocket client applications. Hi, the problem with the extensions is that we are speaking mostly about webbrowsers. So if just a widely used webbrowser in the world decides not to implement an extension (ie: DNS SRV if approbed) then WebSocket service providers could not rely on such mechanism. I suppose the same is true for other extensions (but I'm not sure about their backwards-compatibility and so). In the case of DNS SRV, all the clients must implement it. If not, it's like if it does not exist because no one service provider will want to use DNS SRV knowing that some known clients cannot use them. Just wondering. Regards. -- Iñaki Baz Castillo <ibc@aliax.net>
- Re: [hybi] WebSocket: current status and next ste… Dirkjan Ochtman
- Re: [hybi] WebSocket: current status and next ste… Iñaki Baz Castillo
- [hybi] WebSocket: current status and next steps Salvatore Loreto
- Re: [hybi] WebSocket: current status and next ste… Dirkjan Ochtman
- Re: [hybi] WebSocket: current status and next ste… Greg Wilkins