Date: Fri, 8 Jan 2010 10:20:19 +0100
From: Mike Hommey <mh+notmuch@glandium.org>
To: notmuch@notmuchmail.org
Message-ID: <20100108092019.GA6671@glandium.org>
References: <874oo7hex2.fsf@yoom.home.cworth.org>
	<87y6lewqtw.fsf@convex-new.cs.unb.ca>
	<87638i75sz.fsf@home.veldthuis.com> <1260227209-sup-184@riseup.net>
	<874oo22blf.fsf@yoom.home.cworth.org>
	<20100108025620.GB28357@lapse.rw.madduck.net>
	<20100108080636.GA26839@glandium.org>
	<20100108090317.GB735@lapse.rw.madduck.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100108090317.GB735@lapse.rw.madduck.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [notmuch] Quick thoughts on a notmuch daemon
Precedence: list

On Fri, Jan 08, 2010 at 10:03:21PM +1300, martin f krafft wrote:
> also sprach Mike Hommey <mh+notmuch@glandium.org> [2010.01.08.2106 +1300]:
> > I'm in \o_ (though I won't be in Wellington). I've been thinking
> > about a fuse filesystem on top of notmuch for a while.
> 
> Grand news to see you interested! A FUSE filesystem is <25 functions
> to implement, and each function is basically an entity of its own
> and thus highly parallisable. Once we agreed on a general mapping
> between filesystem i/o and notmuch interaction, 25 of us can write
> a function each and be done. How's that for collaboration? ;)

FYI, I have a good experience writing fuse filesystems, both with
high-level and low-level APIs. I'd avise to use the low-level API, which
allows for better performance.

Mike