Re: [hybi] Random Responses

Greg Wilkins <gregw@webtide.com> Mon, 13 April 2009 00:22 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 7D4C13A6812 for <hybi@core3.amsl.com>; Sun, 12 Apr 2009 17:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level:
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 HcBK9c6w1yiO for <hybi@core3.amsl.com>; Sun, 12 Apr 2009 17:22:30 -0700 (PDT)
Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.186]) by core3.amsl.com (Postfix) with ESMTP id 94F663A6C2C for <hybi@ietf.org>; Sun, 12 Apr 2009 17:22:30 -0700 (PDT)
Received: by ti-out-0910.google.com with SMTP id 24so1791431tim.14 for <hybi@ietf.org>; Sun, 12 Apr 2009 17:23:40 -0700 (PDT)
Received: by 10.110.5.14 with SMTP id 14mr8138289tie.40.1239582220236; Sun, 12 Apr 2009 17:23:40 -0700 (PDT)
Received: from ?10.10.1.12? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id d4sm8321281tib.28.2009.04.12.17.23.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 12 Apr 2009 17:23:39 -0700 (PDT)
Message-ID: <49E28603.8030407@webtide.com>
Date: Mon, 13 Apr 2009 10:23:31 +1000
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090319)
MIME-Version: 1.0
To: hybi@ietf.org
References: <8A829FEA-0EF2-46D6-974D-0EB237FF2728@lindenlab.com> <Pine.LNX.4.62.0904090030580.19453@hixie.dreamhostps.com> <A66ED417-B7AB-4138-B8DE-31323A4DC0C1@lindenlab.com> <49E1518E.7050402@webtide.com> <20090412213257.GL4394@shareable.org>
In-Reply-To: <20090412213257.GL4394@shareable.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Random Responses
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: Mon, 13 Apr 2009 00:22:31 -0000

Jamie,

excellent information and insight in this and your other messages.

I think it is very valuable to look at existing protocols like
BEEP and to identify/enumerate their deficiencies. Straw men
are useful (and others probably appreciate not having me
continue to use websocket for that purpose :)

I've tried to capture a lot of this recent conversation on the
wiki: http://trac.tools.ietf.org/bof/trac/wiki/HyBi

I've added a new section called "Candidates Requirements" where
I list/describe the attributes of a protocol that people have
identified as good (although there is no consensus if all are
indeed good and/or needed).

For each proposal I've listed some pros and cons, mostly
against candidate requirements.    It would be good if others
could sanitize those for any biases coming from me.


I've also added a "Asynchronous HTTP" proposal based on the
description you gave.   You allude to existing proposals for
such a thing - do you have references to those?



cheers