DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:to:subject:date:message-id:user-agent:mime-version
	:content-type;
	b=vdzx3T4lHifOtRp0hei/DoFCnaEBHltE+MLth/SSQdXOU0MwC/BWvM7vUW4M277BuV
	FDONPo9rcuS9a3acyq2pP+GreGktvAegwyv2cEqtN5S3vVWENG6NoOURHBPAC1NlLJ67
	CjOJJHNFmQL3T5t0SIBXKj3yB+aAsrndvKlaU=
From: Paul R <paul.r.ml@gmail.com>
To: notmuch@notmuchmail.org
Date: Tue, 02 Mar 2010 16:26:10 +0100
Message-ID: <87aauqsq25.fsf@aspirouf.lan>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [notmuch] an other ready-to-use store option for notmuch : CouchDB
Precedence: list

Hi,

couchDB is a document-oriented database. It stores documents, IOW
key-value pairs, under a unique ID. These documents are retrieved
through views and queries. A mail with some tags and some mime parts is
a perfect exemple of what couchdb call a "document".

CouchDB databases can be replicated and synced in both directions.
Conflicts are lazily handled.

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. Put a couchDB replica somewhere accessible, push new IMAP mails on
it, then sync as many machines as you want with this central couchDB
store.


-- 
  Paul