IETF Logo Mail Archive

Re: [hybi] Reliable message delivery (was Re: Technical feedback.)

Mridul Muralidharan <mridulm80@yahoo.com> Wed, 03 February 2010 16:53 UTC

Return-Path: <mridulm80@yahoo.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 B6CB128C0E3 for <hybi@core3.amsl.com>; Wed, 3 Feb 2010 08:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level:
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, RELAY_IS_203=0.994]
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 B6qy6dwmtcMs for <hybi@core3.amsl.com>; Wed, 3 Feb 2010 08:53:28 -0800 (PST)
Received: from web95403.mail.in2.yahoo.com (web95403.mail.in2.yahoo.com [203.104.18.227]) by core3.amsl.com (Postfix) with SMTP id 818233A6B1F for <hybi@ietf.org>; Wed, 3 Feb 2010 08:53:27 -0800 (PST)
Received: (qmail 97640 invoked by uid 60001); 3 Feb 2010 16:54:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1265216046; bh=bDWg96P6Nx7L74jm8YLpNv554R1Ur7gSp0sbnWJLXyw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rZua5uKKKPb6hz+ml+WPVvvWZPKIPola6pCEtzlB/bOCcQPKdBwCuQD1ciKEiy8kA+gIhwBa7+qAPNhIPWs/aftpvPEzlLVpQeNzkevKjnaEqYwexNLEeHSA1Qobk9P2nkuvBL4HkvMAtw58CW5X4uEzisiL1mh9EDCJaHXv5iI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=SNrkr5QlE4zxQqM9L5+vIpAbiGrWHsGuxQrE4J0xsYW3KNgqqcTJwHkBBhxs7FVHtVFlDphXxwHBUAcN/dAyvQv62lEi+TbrHuJtz/kXG7cxCz9IXXDdwskEdY63NzzQVTO5PPuohKsT0NvEZi7P3IOWT6KXva+gakUzGQnNZ4Q=;
Message-ID: <292090.96637.qm@web95403.mail.in2.yahoo.com>
X-YMail-OSG: a1OcUXAVM1lbNiaarWBSB.I1xYEDhgO5jMn_XTOq_jm7OOeIgrvoqpp1bwwzOg7KHq9CUy3PtOuRcRK9ktiEGE8HT4OFghdxHnHTQc.vGdjIsDfzMl7y9GPlPB1lzHedo7BOXi.HiX7Nfd4f6tluU0gp5WPuNCy2CBWPfetUEMTF1hTzThXP5FTcBmTN.tVh04LW726URAF88tlCjOiLOIuHPmSyGBEItGGiox6mklPqi1qg_m4lv1EjasVT8vuu_iERRWj7TuOlM3k3xqusEn2xekyTPb_AIOtUATZ7u11swSzn
Received: from [203.83.248.37] by web95403.mail.in2.yahoo.com via HTTP; Wed, 03 Feb 2010 22:24:06 IST
X-Mailer: YahooMailClassic/9.1.10 YahooMailWebService/0.8.100.260964
Date: Wed, 03 Feb 2010 22:24:06 +0530
From: Mridul Muralidharan <mridulm80@yahoo.com>
To: Pieter Hintjens <ph@imatix.com>, Maciej Stachowiak <mjs@apple.com>
In-Reply-To: <06912AB8-D55D-46F4-AAEC-0A2146FB3BB8@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
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: Wed, 03 Feb 2010 16:53:28 -0000


--- On Wed, 3/2/10, Maciej Stachowiak <mjs@apple.com> wrote:

> From: Maciej Stachowiak <mjs@apple.com>
> Subject: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
> To: "Pieter Hintjens" <ph@imatix.com>
> Cc: "hybi@ietf.org" <hybi@ietf.org>
> Date: Wednesday, 3 February, 2010, 9:29 PM
> 
> On Feb 3, 2010, at 7:51 AM, Pieter Hintjens wrote:
> 
> > On Wed, Feb 3, 2010 at 3:10 PM, Greg Wilkins <gregw@webtide.com>
> wrote:
> > 
> >> I don't think you can assume that most websocket
> using software
> >> and/or subprotocols will have the same developer
> working on
> >> the client side and the server side.
> > 
> > I've never seen a protocol that makes this assumption
> and it is a
> > quite extraordinary one from the perspective of
> interoperabilty.
> > 
> > Ian, could you elaborate please?  I do not
> understand your intention
> > in making this statement, nor how significant it is to
> implementing
> > WebSocket.
> 
> The likely deployments of WebSocket are going to be one of
> these:
> 
> JavaScript code running in a browser --> browser's
> WebSocket implementation ====> WebSocket service that
> directly implements the protocol
> 
> JavaScript code running in a browser --> browser's
> WebSocket implementation ====> generic WebSocket server
> --> service code


Is hybi expected to be limited only to javascript or even browser based clients ?
I was assuming other clients might also be interested in leveraging it ? (if nothing else, for async notifications on top of http).


Regards,
Mridul


> 
> 
> Ian is saying that he thinks the JS code running in the
> browser and the specific WebSocket service are likely to be
> created by the same entity on some level, and he apparently
> thinks it is likely that many WebSocket services will
> implement the protocol directly rather than use any kind of
> framework or standard server. Note though that the browser
> code that implements the client side of the WebSocket
> protocol will almost never be written by the same party.
> Also, if the WebSocket service accepts cross-site
> connections, the assumption will not be true at all.
> 
> Regards,
> Maciej
> 
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
> 


      Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/

v2.23.0 | Report a Bug | By Email