Re: [hybi] email granularity, was: WebSockets feedback
Julian Reschke <julian.reschke@gmx.de> Thu, 15 April 2010 19:24 UTC
Return-Path: <julian.reschke@gmx.de>
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 3763A28C1CA for <hybi@core3.amsl.com>; Thu, 15 Apr 2010 12:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.053
X-Spam-Level:
X-Spam-Status: No, score=-4.053 tagged_above=-999 required=5 tests=[AWL=-1.454, 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 HwavNQyAMyEH for <hybi@core3.amsl.com>; Thu, 15 Apr 2010 12:24:15 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id F29FC3A69F3 for <hybi@ietf.org>; Thu, 15 Apr 2010 12:22:13 -0700 (PDT)
Received: (qmail invoked by alias); 15 Apr 2010 19:21:56 -0000
Received: from p508FCE13.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.206.19] by mail.gmx.net (mp061) with SMTP; 15 Apr 2010 21:21:56 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/l1q9FQ+blHikb4RuZ2M92eLsmdn5O8Kfn5joNvP FL3JLuWEsEuSdP
Message-ID: <4BC76724.5090307@gmx.de>
Date: Thu, 15 Apr 2010 21:21:08 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <B578CFED7FE85644A170F4F7C9D52692019544C5@ESESSCMS0361.eemea.ericsson.se> <3d5f2a811003150230sdeb4f78hbdece96e5c742cfc@mail.gmail.com> <de17d48e1003180316w3dda1a3fo7db8b357925ec3f8@mail.gmail.com> <p2o3d5f2a811003310031x5dce7e9cs86a5a8981cd23c1d@mail.gmail.com> <Pine.LNX.4.64.1004140032040.875@ps20323.dreamhostps.com> <w2y5821ea241004142323h949c0b07l771171500a625a6c@mail.gmail.com> <4BC6DD89.4060502@gmx.de> <r2x5821ea241004150244ud3cb79bt757049890bf3d9ab@mail.gmail.com> <Pine.LNX.4.64.1004151908320.23507@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1004151908320.23507@ps20323.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.66000000000000003
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] email granularity, was: WebSockets 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: Thu, 15 Apr 2010 19:24:21 -0000
On 15.04.2010 21:10, Ian Hickson wrote: > ... > This has been the way Web Socket feedback has been handled for years > before this working group was created, and over the years I've had > multiple people tell me they prefer this model. However, I'm happy to do > whatever the chairs want me to do. > ... It might have been a good thing while you used the WHATWG mailing list, where many many other topics are discussed as well. But *this* mailing list is for the various Hybi specs, so IMHO the right (and common) way to handle things is to have one mailing list thread per topic, and, optimally, not to mix process questions with technical questions ;-) I'm sure the chairs will correct me if they see this differently. Best regards, Julian
- [hybi] Revised WebSocket Feedback Vladimir Katardjiev
- Re: [hybi] Revised WebSocket Feedback Takeshi Yoshino
- Re: [hybi] Revised WebSocket Feedback Fumitoshi Ukai (鵜飼文敏)
- Re: [hybi] Revised WebSocket Feedback Takeshi Yoshino
- [hybi] WebSockets feedback Ian Hickson
- Re: [hybi] WebSockets feedback Pieter Hintjens
- Re: [hybi] WebSockets feedback Greg Wilkins
- [hybi] email granularity, was: WebSockets feedback Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… Anne van Kesteren
- Re: [hybi] email granularity, was: WebSockets fee… Ian Hickson
- Re: [hybi] email granularity, was: WebSockets fee… Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… Michael Carter
- Re: [hybi] email granularity, was: WebSockets fee… Justin Erenkrantz
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… Julian Reschke
- Re: [hybi] email granularity, was: WebSockets fee… SM
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… Tim Bray
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… SM
- Re: [hybi] email granularity, was: WebSockets fee… Ian Hickson
- Re: [hybi] email granularity, was: WebSockets fee… Maciej Stachowiak
- Re: [hybi] email granularity, was: WebSockets fee… Pieter Hintjens
- Re: [hybi] email granularity, was: WebSockets fee… Greg Wilkins
- Re: [hybi] email granularity, was: WebSockets fee… L.Wood