From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.224.197 with SMTP id ip5cs217898icb; Tue, 22 Feb 2011 13:53:43 -0800 (PST) Received: by 10.224.216.10 with SMTP id hg10mr2754872qab.101.1298411623181; Tue, 22 Feb 2011 13:53:43 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id x11si13876738qcm.77.2011.02.22.13.53.41; Tue, 22 Feb 2011 13:53:42 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id B43371858300; Tue, 22 Feb 2011 16:53:41 -0500 (EST) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 65BF43C8056 for ; Tue, 22 Feb 2011 16:27:31 -0500 (EST) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1Przn9-0002ZJ-SI for sup-devel@rubyforge.org; Tue, 22 Feb 2011 21:29:07 +0000 From: William Morgan To: sup-devel In-reply-to: <1298400274-sup-4941@tilus.net> References: <1298320404-sup-5972@masanjin.net> <1298400274-sup-4941@tilus.net> Date: Tue, 22 Feb 2011 21:29:07 +0000 Message-Id: <1298409714-sup-1926@masanjin.net> User-Agent: Sup/git 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: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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. > Do you have considerations wrt to programmatical thread browsing and > editing API? I suspect won't get into that level of detail. The API will be more along the lines of "give me thread 6" and you'll get a tree of message ids back, and on the client side you can represent that however you like. Unless there's a compelling case for handling portions of threads at the API level. > > - Allow concurrent access from multiple clients. > > Since the first post on sup-server I've been nurturing the idea of "fat" > sup-client for maemo/meego. That would be great. I would like an Android client while you're at it. :) > Would it be time to go for https://github.com/mikel/mail now? It would be > supported and actively developed and I really like the API. As a > downside, depending on activesupport pulls in a whole a lot of fluff and > using treetop may suggest that parsing might hog a little more cpu and > memory than is absolutely necessary. I looked at it, but the dependency on activesupport is a dealbreaker for me. There's no way I would pull that pile of Rails shit into Sup. RMail is not great and I don't like using it, but it really is the best thing I've found so far. I think I have whipped it into shape pretty well in heliotrope. > Who would give us bindings to GMime and wrap it inside Mail API... I would use GMime bindings in a heartbeat. -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel