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 adam.kocoloski@gmail.com
 designates 209.85.128.42 as permitted sender)
Subject: Re: Attachment replication
References: 
 <CAGHTdUWvU4NfWcoKYzDHhKsKLWrdJYtdxqOeVA_kd6U01BqD2Q@mail.gmail.com>
From: Adam Kocoloski <adam.kocoloski@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CAGHTdUWvU4NfWcoKYzDHhKsKLWrdJYtdxqOeVA_kd6U01BqD2Q@mail.gmail.com>
Message-Id: <5FFF37C5-D2B2-4F2C-8CCE-93E25773CC43@gmail.com>
Date: Sat, 3 Aug 2013 20:52:28 -0400
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Yes, the system provides that guarantee. Some versions of CouchDB transfers t=
he attachments in separate requests, but when the doc is in the target's _ch=
anges you can be assured that all of its attachments have made the trip.  Ch=
eers,

Adam

On Aug 3, 2013, at 5:36 PM, Nick North <north.n@gmail.com> wrote:

> If I create a document with attachments in a single HTTP call, either
> inline or in MIME format, does it all replicate as a single unit, or do th=
e
> attachments replicate separately? I'd like to know that, if the document
> turns up in the changes field of a replica, then both the document and the=

> attachments can be requested immediately. Thanks for your help,
>=20
> Nick North