Re: [hybi] Serf support for BWTP

Greg Wilkins <gregw@webtide.com> Sat, 19 December 2009 00:36 UTC

Return-Path: <gregw@webtide.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 71A6B3A69ED for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 d3edNzceCOFG for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:36:02 -0800 (PST)
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id B69CA3A69E6 for <hybi@ietf.org>; Fri, 18 Dec 2009 16:36:02 -0800 (PST)
Received: by yxe30 with SMTP id 30so4113067yxe.29 for <hybi@ietf.org>; Fri, 18 Dec 2009 16:35:44 -0800 (PST)
Received: by 10.90.11.30 with SMTP id 30mr5097800agk.42.1261182944310; Fri, 18 Dec 2009 16:35:44 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 15sm1245353gxk.0.2009.12.18.16.35.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Dec 2009 16:35:43 -0800 (PST)
Message-ID: <4B2C1FD2.9060102@webtide.com>
Date: Sat, 19 Dec 2009 11:35:30 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Justin Erenkrantz <justin@erenkrantz.com>
References: <5c902b9e0912180032o33d58da5hf3411baeb1fc5f7f@mail.gmail.com>
In-Reply-To: <5c902b9e0912180032o33d58da5hf3411baeb1fc5f7f@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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:36:04 -0000

Justin,

Wow! cool!   Working code rules!!!

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).

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 :)

cheers



Justin Erenkrantz wrote:
> Hi hybi@,
> 
> Out of some stuff that's been done with CREST [1], I got pointed at
> BWTP and decided to implement it in Serf [2].  A colleague of mine at
> UC Irvine is implementing BWTP with PLT Scheme for some CREST stuff
> he's doing.  (In short, CREST would benefit from having an async
> protocol.)
> 
> If ya'll haven't followed the Twitter conversation between me and
> Hixie over the last few days, I've pretty much come to the same
> conclusions regarding "Web Sockets" RFC that Greg Wilkins did much
> earlier.  (Kudos to Greg!)  I guess that Hixie has tried to write his
> RFC drafts in a way that stresses one particular way of writing a
> client - but for a pure async client library like Serf, the
> description in the RFC is pretty impenetrable...and, in my mind, not
> very helpful when it comes to writing an independent implementation.
> So, I found BWTP a lot easier to implement...and so I did.
> 
> The BWTP implementation in Serf isn't perfect and there's probably
> more to do, but it'll suffice for now.  Though there do seem to be
> some errors in the BWTP RFC, but I'm not sure if Greg is updating the
> BWTP RFC drafts or not.  If so, I'm happy to post about those apparent
> errors as well.
> 
> Anyway, Hixie asked that I subscribe/post to the IETF list, so here I
> am.  =)  -- justin
> 
> 1. http://www.erenkrantz.com/CREST/
> 2. http://code.google.com/p/serf/
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi