Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of b.candler@pobox.com
 designates 64.74.157.62 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to:cc
	:subject:message-id:references:mime-version:content-type
	:in-reply-to; q=dns; s=sasl; b=p21x/pM5fNVenQQkCttEe2RYT5eHsBJ54
	gkLVto/SSqSEcMQ75Folffr1VqNwAXsNV3gH0AZAHaSmI5rPbY2jLlh0j+tIOPy+
	ZmMckOJTcpqCZ8nEBoi+u4nQm8KtYsljZayXqRWcx2hCtPiIDimuvpVm8+c/qYEh
	6pAv0Cbxs0=
Date: Tue, 3 Nov 2009 09:43:08 +0000
From: Brian Candler <B.Candler@pobox.com>
To: Damien Katz <damien@apache.org>
Cc: user@couchdb.apache.org
Subject: Re: all_or_nothing=true and replication
Message-ID: <20091103094308.GC9729@uk.tiscali.com>
References: <01DCAC9E-0125-46EA-876E-12B685C40DFC@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01DCAC9E-0125-46EA-876E-12B685C40DFC@apache.org>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)

On Sun, Nov 01, 2009 at 05:36:18PM -0500, Damien Katz wrote:
> Yes, you can make a situation where somehow a user has legal updates to 
> certain conflicts, but not others, on a particular node A. On some other 
> node B, somehow the security was different and he was allowed to update 
> all the docs. Then an attempt to merge all the conflicts into the 
> document the user didn't really have edit access too will not be  
> replicated from node B to node A.
>
> It's a contrived situation, but possible with misconfigured or updated  
> security settings that haven't propagated.

This is definitely something that I need to add to the
Replication_and_conflicts page.

When you talk about security mechanisms, I know of "validate_doc_update",
but are there other things which can affect whether a document is replicated
or not? (e.g. I've heard talk of a filtered _changes feed, I don't know if
that's implemented yet). I'd like to make sure I cover all bases.

On a related point: is it possible to configure a database to stop people
*pulling* certain documents? For example, if I want to allow people to read
and replicate user documents but not _design documents?

Thanks,

Brian.