IETF Logo Mail Archive

Re: [hybi] Serf support for BWTP

Justin Erenkrantz <justin@erenkrantz.com> Sat, 19 December 2009 00:46 UTC

Return-Path: <justin.erenkrantz@gmail.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 E68593A69CD for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:46:02 -0800 (PST)
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 TJTTgRjCh9+R for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:46:02 -0800 (PST)
Received: from mail-pw0-f50.google.com (mail-pw0-f50.google.com [209.85.160.50]) by core3.amsl.com (Postfix) with ESMTP id 3F99C3A6967 for <hybi@ietf.org>; Fri, 18 Dec 2009 16:46:02 -0800 (PST)
Received: by pwi20 with SMTP id 20so2412009pwi.29 for <hybi@ietf.org>; Fri, 18 Dec 2009 16:45:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=43ylV1gHYYcJ9JjlUXQG0L5P/eADt4UVa2ZoPTBn+BA=; b=wL2B8t31eThQ3CXMF6Rn3r3uWxWQyiPDug6Nzk5DfY9jM32LufaF52bEZtQDYcypvV Bmu9BKiJL52PV8lCPnSRdW9KkwK7Cc96/sc9Z2q1V/Y1an9zwS+ULo6+N5SMT5ucMPGT xKfmP8B6Lf/cujiOC/OW03iQrWoRb2VXYnol0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=LWT+uj1SfIli3fmlk1pau3ex4seSlJ8pbH2lwd3jqOg0maIRh1haoyYYj06tDoU0hz 2tqvLLGqFGCBdj97KON/wekj0m4fAlnb8PRkmdGaeC7eemR3PMPadV0r93BiLTo87/Cx fMDEGyvSX1awzaSjTykxE3HIT9tWUSfip5BpI=
MIME-Version: 1.0
Sender: justin.erenkrantz@gmail.com
Received: by 10.142.249.40 with SMTP id w40mr2917631wfh.344.1261183544545; Fri, 18 Dec 2009 16:45:44 -0800 (PST)
In-Reply-To: <4B2C1FD2.9060102@webtide.com>
References: <5c902b9e0912180032o33d58da5hf3411baeb1fc5f7f@mail.gmail.com> <4B2C1FD2.9060102@webtide.com>
Date: Fri, 18 Dec 2009 16:45:44 -0800
X-Google-Sender-Auth: 06deddd4109ccc93
Message-ID: <5c902b9e0912181645p579c3042ia64b1561c47b65ed@mail.gmail.com>
From: Justin Erenkrantz <justin@erenkrantz.com>
To: Greg Wilkins <gregw@webtide.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] Serf support for BWTP
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: Sat, 19 Dec 2009 00:46:03 -0000

On Fri, Dec 18, 2009 at 4:35 PM, Greg Wilkins <gregw@webtide.com> wrote:
> Justin,
>
> Wow! cool!   Working code rules!!!

Yah, I find it largely pointless to talk about protocols without
having an implementation to back up what I'm saying.  *grin*

> However, what I'd like to do with BWTP is to update it so that
> it can be easily and efficiently sent over websocket (using
> binary framing) or sent over it's own connection (more or less
> as currently specified).

Hmm.  I'm not quite sure I grok how you would tunnel over websocket, but maybe.

> But currently I'm spending most of my time on Jetty's websocket
> implementation (and using it in cometd), to make sure that we
> have the best websocket implementation that there is... and
> then we can still say that we hate it and that it is not because
> we don't support it :)

Perhaps instead of reading the websocket RFC draft (which I can't
understand anyway), I should look at Jetty's websocket implementation.
 That might make more sense to me...  *grin*  -- justin

v2.29.0 | Report a Bug | By Email | System Status