From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Ben Gamari <bgamari@gmail.com>
In-Reply-To: <1267468550-sup-8956@ben-laptop>
References: <87pr57jvkz.fsf@SSpaeth.de> <87wry2wl7p.fsf@yoom.home.cworth.org>
	<87ljecmnbd.fsf@steelpick.localdomain> <1267459947-sup-6640@ben-laptop>
	<87bpf82c5c.fsf@steelpick.localdomain> <1267468550-sup-8956@ben-laptop>
Date: Mon, 01 Mar 2010 21:20:48 +0100
Message-ID: <878wab3ian.fsf@steelpick.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [notmuch] Introducing notmuchsync
Precedence: list

On Mon, 01 Mar 2010 13:43:24 -0500, Ben Gamari <bgamari@gmail.com> wrote:
> Excerpts from Michal Sojka's message of Mon Mar 01 12:18:55 -0500 2010:
> > > How do you propose that the backends keep track of what mail has been
> > > indexed?
> > 
> > For example by using Xapian metadata:
> > notmuch->xapian_db->set_metadata ("git-head", sha1);
> 
> However, this means that the backend would need to know about the
> indexing database, which seems to me like a implementation detail that
> should be hidden from the backend (perhaps? Maybe not, I suppose). I guess this all
> depends upon how much we want to abstract out the backends.

I do not see why the databse should be hidded. It will be easier to
implement if the backend knows about it. Also, I'm not sure whether this
should be called "backend". From certain point of view Xapian can be
considered as backend and mail store implemetation will be a frontend.

- Michal