From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.224.54.131 with SMTP id q3cs277483qag; Wed, 23 Feb 2011 02:10:22 -0800 (PST) Received: by 10.52.160.3 with SMTP id xg3mr5714601vdb.311.1298455821036; Wed, 23 Feb 2011 02:10:21 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id k12si10847876vcr.144.2011.02.23.02.10.20; Wed, 23 Feb 2011 02:10:21 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id A0E8319783C0; Wed, 23 Feb 2011 05:10:20 -0500 (EST) Received: from mail-bw0-f45.google.com (mail-bw0-f45.google.com [209.85.214.45]) by rubyforge.org (Postfix) with ESMTP id D7309185837F for ; Wed, 23 Feb 2011 04:48:14 -0500 (EST) Received: by bwz16 with SMTP id 16so4090888bwz.18 for ; Wed, 23 Feb 2011 01:48:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:subject:to:in-reply-to :references:mime-version:content-type:content-id; bh=Xxncg/5yE/pEUcU4T730CFeSg4Gb0iP3Z8UcYyg5JBw=; b=ht+6I3KnG4Thc+x4/itDymDMXKKWLqdyOyk/eg92aCe5tczmzhzdAhuZlFt3squb8B gh4mXEwzCxqRwj2PpCqihqyz8jKZXWpMLN3o8mlxjOwjdtq5XeNtEArD3/zhQyJu2TXc Sheu9j5OhaGPX4vl5MRsLUqsr3+gTcO44TE98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:subject:to:in-reply-to:references:mime-version :content-type:content-id; b=LBc3+yg30828VAB7XtZttajxTYt3s4IofcxeZwGRzMgyRv0qzYhI+P+SxI53LbjsC5 tOnjk+kkXtzfacFq0+EhqpRS+lD9EwdmOHZgyam6cK6xgyMja8MWWTWEkYw9x6h2+9d3 BgtzlH0PVQfkH+otrCsPd8VfeOf457dic/l08= Received: by 10.204.76.1 with SMTP id a1mr3540645bkk.5.1298454493544; Wed, 23 Feb 2011 01:48:13 -0800 (PST) Received: from localhost (sk.feydakins.org [94.23.4.142]) by mx.google.com with ESMTPS id v25sm5167536bkt.6.2011.02.23.01.48.11 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Feb 2011 01:48:12 -0800 (PST) Message-ID: <4d64d7dc.5989cc0a.4550.ffffb543@mx.google.com> Date: Wed, 23 Feb 2011 01:48:12 -0800 (PST) From: Nicolas Pouillard To: William Morgan , sup-devel In-Reply-To: <1298409714-sup-1926@masanjin.net> References: <1298320404-sup-5972@masanjin.net> <1298400274-sup-4941@tilus.net> <1298409714-sup-1926@masanjin.net> MIME-Version: 1.0 Content-ID: <12443.1298454490.1@sk.feydakins.org> Subject: Re: [sup-devel] sup-server revisited X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org On Tue, 22 Feb 2011 21:29:07 +0000, William Morgan wrote: > Reformatted excerpts from Tero Tilus's message of 2011-02-22: > > I guess this offers the possibility to add threading to "external state" > > of messages, together with labels. I'd do a whole a lot of more > > prune'n'crafting with my threads if there only was more comfortable > > interface to doing it (admit it, been too lazy to implement it in sup). > > Not quite sure I follow, but the intention is certainly to allow clients to > create and break threads and to present labels as per-thread, rather than > per-message, data. I would not go for "labels on threads" only, here is a list of labels that are more message based than thread based: unread, starred, draft, sent, attachment. And while it would make sense to have special cases for those this also prevents from user defined per message labels. -- Nicolas Pouillard http://nicolaspouillard.fr _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel