DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=sender:from:to:subject:in-reply-to:references:date:message-id
	:mime-version:content-type;
	b=PTJrlnjSO36PFDROR/HVAI3kanfCZaJgyoLKSMxao6gPqDTw7bIeq4oA2mZ5U78/ov
	XUcW/yNwrisV3SsLK/sr516GTKcOz3U+v9qaFdWsU3BZWY0AEyEuv9TjGrT+eG7MoBmM
	agz2U8r5UclsFkdmtU/5PmkFS2x6HZm3Wlts8=
Sender: Jed Brown <five9a2@gmail.com>
From: Jed Brown <jed@59A2.org>
To: Paul R <paul.r.ml@gmail.com>, notmuch@notmuchmail.org
In-Reply-To: <87aauqsq25.fsf@aspirouf.lan>
References: <87aauqsq25.fsf@aspirouf.lan>
Date: Tue, 02 Mar 2010 16:44:15 +0100
Message-ID: <87ocj6hgog.fsf@59A2.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] an other ready-to-use store option for notmuch :
 CouchDB
Precedence: list

On Tue, 02 Mar 2010 16:26:10 +0100, Paul R <paul.r.ml@gmail.com> wrote:
> CouchDB databases can be replicated and synced in both directions.
> Conflicts are lazily handled.

I've wondered about this.  An interesting property would be lack of a
global lock, which is one of the reasons why people are either not
having notmuch-new run automatically, or are working around the errors
when the database is locked, and thus all the talk about having a
notmuch daemon or other method of handling asynchronous actions.

The advantage of the current system is that the mail store remains
current, but untouched.  Importing into something like CouchDB or
MongoDB would seem to interfere with "point at a directory and go, with
no full copy".

> People here often call for facilities to read mail with notmuch from
> different places. An unidirectional imap-to-couchDB, plus a couchDB
> backend for notmuch, should give enough flexibility to achieve this
> goal.

I thought people were asking to be able to read messages from other
places *with other tools*, such as phones or webmail.  This would
require 2-way sync with IMAP.

Jed