unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mike Hommey <mh+notmuch@glandium.org>
To: notmuch@notmuchmail.org
Subject: Re: Quick thoughts on a notmuch daemon
Date: Fri, 8 Jan 2010 10:20:19 +0100	[thread overview]
Message-ID: <20100108092019.GA6671@glandium.org> (raw)
In-Reply-To: <20100108090317.GB735@lapse.rw.madduck.net>

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

  reply	other threads:[~2010-01-08  9:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 22:27 Quick thoughts on a notmuch daemon Carl Worth
2009-12-07 19:02 ` David Bremner
2009-12-07 22:55   ` Marten Veldthuis
2009-12-07 23:51     ` micah anderson
2009-12-08  7:01       ` Carl Worth
2010-01-08  2:56         ` martin f krafft
2010-01-08  8:06           ` Mike Hommey
2010-01-08  9:03             ` martin f krafft
2010-01-08  9:20               ` Mike Hommey [this message]
2010-01-08 10:26                 ` martin f krafft
2010-01-09  5:51                   ` Mike Hommey
2009-12-08 19:29 ` Michiel Buddingh'
2009-12-09 22:13 ` Ruben Pollan
2010-02-20  1:09 ` Ruben Pollan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100108092019.GA6671@glandium.org \
    --to=mh+notmuch@glandium.org \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).