IETF Logo Mail Archive

Re: [hybi] how do we move forward on agreeing on framing?

John Tamplin <jat@google.com> Thu, 19 August 2010 16:51 UTC

Return-Path: <jat@google.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 455E93A69A9 for <hybi@core3.amsl.com>; Thu, 19 Aug 2010 09:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.797
X-Spam-Level:
X-Spam-Status: No, score=-104.797 tagged_above=-999 required=5 tests=[AWL=1.179, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 tKEXSnHKrZI0 for <hybi@core3.amsl.com>; Thu, 19 Aug 2010 09:51:15 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id C74AB3A696F for <hybi@ietf.org>; Thu, 19 Aug 2010 09:51:14 -0700 (PDT)
Received: from hpaq2.eem.corp.google.com (hpaq2.eem.corp.google.com [172.25.149.2]) by smtp-out.google.com with ESMTP id o7JGpmVu021738 for <hybi@ietf.org>; Thu, 19 Aug 2010 09:51:48 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1282236709; bh=6GsY7tcwuJIxXVNTRVfDb30Lq6Q=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=ekOH2yWia8foAlvSu6jL6SEGMTZ3vQ4/SY0uAxdeV2rUFw7/o8CV66ZvuSy9kei2/ omxUX24bePo7WuqkiGfKw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=HI16MLW3s0pM4hN8XuWhg2ZL7juEuBEeXgOj0rNey92MU0CbYK7fNyBQsO7+s3EwL Fq8c0c3lokg4hXruXyK0Q==
Received: from yxj4 (yxj4.prod.google.com [10.190.3.68]) by hpaq2.eem.corp.google.com with ESMTP id o7JGpbIn008362 for <hybi@ietf.org>; Thu, 19 Aug 2010 09:51:47 -0700
Received: by yxj4 with SMTP id 4so1203041yxj.15 for <hybi@ietf.org>; Thu, 19 Aug 2010 09:51:47 -0700 (PDT)
Received: by 10.150.11.12 with SMTP id 12mr228390ybk.280.1282236706623; Thu, 19 Aug 2010 09:51:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.60.3 with HTTP; Thu, 19 Aug 2010 09:51:26 -0700 (PDT)
In-Reply-To: <1282231803.22142.649.camel@vulcan.aspl.local>
References: <AANLkTineuhvGsC_vca6AiAX8OmHdkE-7s7rA1DQtjtMm@mail.gmail.com> <1282231803.22142.649.camel@vulcan.aspl.local>
From: John Tamplin <jat@google.com>
Date: Thu, 19 Aug 2010 12:51:26 -0400
Message-ID: <AANLkTinsfhux1fVfYUdBFE3_ets3GLnynWoKOJ-f0+fk@mail.gmail.com>
To: Francis Brosnan Blazquez <francis@aspl.es>
Content-Type: multipart/alternative; boundary="000e0cd6aca26bd8c3048e2fff92"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] how do we move forward on agreeing on framing?
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: Thu, 19 Aug 2010 16:51:16 -0000

On Thu, Aug 19, 2010 at 11:30 AM, Francis Brosnan Blazquez
<francis@aspl.es>wrote:

> I think it is taking to much attention to include advanced features in
> the base protocol, or to define extensions that allow them, especially
> when those features can be implemented by protocols already defined like
> BEEP [1].
>

Unless you are suggesting that BEEP be adopted as the WebSocket protocol, I
am not sure how the fact that BEEP supports these things helps us here.  I
think BEEP is a bit heavy-weight for what we are trying to accomplish here,
though certainly it can be a source of ideas.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email