IETF Logo Mail Archive

Re: [hybi] Is there a traffic jam?

Mike Dierken <mike@dierken.com> Tue, 14 April 2009 18:35 UTC

Return-Path: <mike@dierken.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 739A63A6E18 for <hybi@core3.amsl.com>; Tue, 14 Apr 2009 11:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 c+EWQcqVL18B for <hybi@core3.amsl.com>; Tue, 14 Apr 2009 11:35:33 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by core3.amsl.com (Postfix) with ESMTP id 41AD828C1F8 for <hybi@ietf.org>; Tue, 14 Apr 2009 11:35:33 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id k40so2351413rvb.49 for <hybi@ietf.org>; Tue, 14 Apr 2009 11:36:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.139.4 with SMTP id m4mr3281817rvd.292.1239734204528; Tue, 14 Apr 2009 11:36:44 -0700 (PDT)
In-Reply-To: <50044.193.253.216.132.1239692803.squirrel@mail1.webfaction.com>
References: <03BCE29D-7AA5-4128-9F61-446E0229479A@lindenlab.com> <E51D5B15BFDEFD448F90BDD17D41CFF105A0C476@AHQEX1.andrew.com> <Pine.LNX.4.62.0904140002360.10339@hixie.dreamhostps.com> <49E3D66C.5060002@webtide.com> <49E3D731.30305@mozilla.com> <79ea848f0904131727w5d4bc0d8kc9914d26080a01fc@mail.gmail.com> <49E3DB47.5060801@webtide.com> <49E428DD.3070803@defuze.org> <086D9C6DD2C9407D8D8CE0601FF0FD4A@mercury> <50044.193.253.216.132.1239692803.squirrel@mail1.webfaction.com>
Date: Tue, 14 Apr 2009 11:36:44 -0700
Message-ID: <3f5bf96b0904141136j6bc6e179w34af8ebb449b8d70@mail.gmail.com>
From: Mike Dierken <mike@dierken.com>
To: sh@defuze.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: hybi@ietf.org
Subject: Re: [hybi] Is there a traffic jam?
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: Tue, 14 Apr 2009 18:35:38 -0000

I was thinking the applet would expose the 'web socket' API (or
equivalent) and the app would be built with JavaScript. This would be
a way to prototype an approach that created a sibling of
XMLHttpRequest, but meant for receiving unsolicited requests in a page
- something like XMLHttpServer (but without the XML part).



On Tue, Apr 14, 2009 at 12:06 AM, Sylvain Hellegouarch <sh@defuze.org> wrote:
>
>>
>>> The question I have now is, what does precisely stop browsers
>>> from offering a raw TCP socket API at the Javascript level?
>>>
>> I thought that was available, via object/applet style plug-ins.
>>
>
> But if that was the solution we wouldn't have this discussion. It's
> because people want to/have to write their application in javascript that
> there is a need for a better solution than what exists now.
>
> Perhaps the reason BEEP has never taken off is because it's so versatile
> that it ultimately creates a bigger mismatch. I'm afraid WS might follow
> the same trend.
>
> - Sylvain
> --
> Sylvain Hellegouarch
> http://www.defuze.org
>

v2.23.0 | Report a Bug | By Email