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 jens@mooseyard.com designates
 208.97.132.145 as permitted sender)
Message-Id: <09BA5434-3B20-42D0-8450-06E25993BF9C@mooseyard.com>
From: Jens Alfke <jens@mooseyard.com>
To: user@couchdb.apache.org
In-Reply-To: <5118A1E1-A51C-4722-BBA8-71F6FAF6B181@apache.org>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Getting "unauthorized" errors replicating from jchris's
 twitter-client-design
Date: Sun, 15 Feb 2009 10:04:19 -0800
References: <7C8D756C-FD0A-4665-8583-49F992973138@mooseyard.com>
 <5118A1E1-A51C-4722-BBA8-71F6FAF6B181@apache.org>


On Feb 15, 2009, at 2:01 AM, Jan Lehnardt wrote:

> Chris has set up his instance so that we all can read, but only
> he can write to it. At the moment, replication does not fully
> work with authentication-enabled replication sources. But
> this is being worked on.

Ah, OK. This must have worked when he posted the blog entry 3 months =20
ago, but broken since.

The things I'm most interested in doing with CouchDB would involve =20
both replication and access control, so this is a problem for me. Do =20
you have an idea when this bug will be fixed? And/or a link to the =20
issue tracker? Thanks!

> The book is describing reality for when it is going to be
> released. Some things we write about might not yet work
> as described.

The things from the book actually seem to be working in my build. This =20=

example came from his blog.

=97Jens=