1 Return-Path: <mh@glandium.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 779BC431FBC
\r
6 for <notmuch@notmuchmail.org>; Fri, 8 Jan 2010 01:20:25 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id jZhtSU25MPMv for <notmuch@notmuchmail.org>;
\r
11 Fri, 8 Jan 2010 01:20:25 -0800 (PST)
\r
12 Received: from vuizook.err.no (vuizook.err.no [85.19.221.46])
\r
13 by olra.theworths.org (Postfix) with ESMTP id 131E3431FAE
\r
14 for <notmuch@notmuchmail.org>; Fri, 8 Jan 2010 01:20:25 -0800 (PST)
\r
15 Received: from cha92-13-88-165-248-19.fbx.proxad.net ([88.165.248.19]
\r
17 by vuizook.err.no with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
\r
18 (Exim 4.69) (envelope-from <mh@glandium.org>) id 1NTB12-0000Xe-NT
\r
19 for notmuch@notmuchmail.org; Fri, 08 Jan 2010 10:20:23 +0100
\r
20 Received: from mh by jigen with local (Exim 4.71) (envelope-from <mh@jigen>)
\r
22 for notmuch@notmuchmail.org; Fri, 08 Jan 2010 10:20:19 +0100
\r
23 Date: Fri, 8 Jan 2010 10:20:19 +0100
\r
24 From: Mike Hommey <mh+notmuch@glandium.org>
\r
25 To: notmuch@notmuchmail.org
\r
26 Message-ID: <20100108092019.GA6671@glandium.org>
\r
27 References: <874oo7hex2.fsf@yoom.home.cworth.org>
\r
28 <87y6lewqtw.fsf@convex-new.cs.unb.ca>
\r
29 <87638i75sz.fsf@home.veldthuis.com> <1260227209-sup-184@riseup.net>
\r
30 <874oo22blf.fsf@yoom.home.cworth.org>
\r
31 <20100108025620.GB28357@lapse.rw.madduck.net>
\r
32 <20100108080636.GA26839@glandium.org>
\r
33 <20100108090317.GB735@lapse.rw.madduck.net>
\r
35 Content-Type: text/plain; charset=us-ascii
\r
36 Content-Disposition: inline
\r
37 In-Reply-To: <20100108090317.GB735@lapse.rw.madduck.net>
\r
38 X-GPG-Fingerprint: A479 A824 265C B2A5 FC54 8D1E DE4B DA2C 54FD 2A58
\r
39 User-Agent: Mutt/1.5.20 (2009-06-14)
\r
40 Subject: Re: [notmuch] Quick thoughts on a notmuch daemon
\r
41 X-BeenThere: notmuch@notmuchmail.org
\r
42 X-Mailman-Version: 2.1.13
\r
44 List-Id: "Use and development of the notmuch mail system."
\r
45 <notmuch.notmuchmail.org>
\r
46 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
47 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
48 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
49 List-Post: <mailto:notmuch@notmuchmail.org>
\r
50 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
51 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
53 X-List-Received-Date: Fri, 08 Jan 2010 09:20:25 -0000
\r
55 On Fri, Jan 08, 2010 at 10:03:21PM +1300, martin f krafft wrote:
\r
56 > also sprach Mike Hommey <mh+notmuch@glandium.org> [2010.01.08.2106 +1300]:
\r
57 > > I'm in \o_ (though I won't be in Wellington). I've been thinking
\r
58 > > about a fuse filesystem on top of notmuch for a while.
\r
60 > Grand news to see you interested! A FUSE filesystem is <25 functions
\r
61 > to implement, and each function is basically an entity of its own
\r
62 > and thus highly parallisable. Once we agreed on a general mapping
\r
63 > between filesystem i/o and notmuch interaction, 25 of us can write
\r
64 > a function each and be done. How's that for collaboration? ;)
\r
66 FYI, I have a good experience writing fuse filesystems, both with
\r
67 high-level and low-level APIs. I'd avise to use the low-level API, which
\r
68 allows for better performance.
\r