IETF Logo Mail Archive

Re: [hybi] email granularity, was: WebSockets feedback

Justin Erenkrantz <justin@erenkrantz.com> Fri, 16 April 2010 06:26 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 9D6003A6B55 for <hybi@core3.amsl.com>; Thu, 15 Apr 2010 23:26:50 -0700 (PDT)
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 W3gmTADCrO8H for <hybi@core3.amsl.com>; Thu, 15 Apr 2010 23:26:50 -0700 (PDT)
Received: from mail-qy0-f184.google.com (mail-qy0-f184.google.com [209.85.221.184]) by core3.amsl.com (Postfix) with ESMTP id C7D873A6B50 for <hybi@ietf.org>; Thu, 15 Apr 2010 23:26:49 -0700 (PDT)
Received: by qyk14 with SMTP id 14so238336qyk.14 for <hybi@ietf.org>; Thu, 15 Apr 2010 23:26:40 -0700 (PDT)
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:received:message-id:subject :from:to:cc:content-type; bh=TUaaAwIGtVNXPOEvwd9bwF3usSBM7DB/bRvZKjoTHjY=; b=Y+ZzFsurmjwgbq2B13Qy82zkV57jwn/sCl3YYs5ZCyD1yyyjfjqMFv1yXLuJ1d6YhY xnY9PQCJ3L8JkD+qjf+dEWsiqH/lUI7RKR9oy+jPL285RNC83PE5+hcwmJa2pZLL14YO dXBEhVCaPAbYvOP76YSRNhxHscmqd4KKP+wGA=
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; b=FzeWIMHFs47+HA2ulx2i/DIPR4Pp51gqgIFbdQaRscR6OKslUArSmdeL+aLoF6If9u YcoJCeuDKQAwKTur0gjwARAXEZodIzRGhWSam+ZCZtF7XgwrBJiwNnLNr+6ByNZYkw05 z0Gl8/p1aBULpEBs+oJNvCVebLRPDTg8zwSiw=
MIME-Version: 1.0
Sender: justin.erenkrantz@gmail.com
Received: by 10.229.17.84 with HTTP; Thu, 15 Apr 2010 23:26:40 -0700 (PDT)
In-Reply-To: <4BC76724.5090307@gmx.de>
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> <4BC76724.5090307@gmx.de>
Date: Thu, 15 Apr 2010 23:26:40 -0700
X-Google-Sender-Auth: 2fa985f30bbd95de
Received: by 10.229.128.82 with SMTP id j18mr1519217qcs.61.1271399200111; Thu, 15 Apr 2010 23:26:40 -0700 (PDT)
Message-ID: <t2n5c902b9e1004152326h78361bfcp87c2fe54138e94c4@mail.gmail.com>
From: Justin Erenkrantz <justin@erenkrantz.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
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: Fri, 16 Apr 2010 06:26:50 -0000

On Thu, Apr 15, 2010 at 12:21 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 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 prefer that we stick to a threaded model: trying to find a response
hidden inside a *huge* post two months after the question was raised
in a completely different thread is very very annoying.  -- justin

v2.23.0 | Report a Bug | By Email