Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Sun, 08 Nov 2009 23:13:44 -0000
Message-ID: <20091108231344.28735.39575@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Trivial_Update_of_=22Replication=22_by_mde?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Replication" page has been changed by mde.
http://wiki.apache.org/couchdb/Replication?action=3Ddiff&rev1=3D15&rev2=3D16

--------------------------------------------------

  The target database has to exist and is not implicitly created. Add `crea=
te_target:true` to the JSON object to create the target database (remote or=
 local) prior to replication. The names of the source and target databases =
do not have to be the same.
  =

  =

- Specifying a local `source` database and a remote `target` database is ca=
lled ''push replication'' and a remote `source` and local `target` is calle=
d ''pull replication''. As of CouchDB 0.9, pull replication is a lot more e=
fficient and error resilient, and it is suggested that you use pull replica=
tion in most cases, especially if your documents are large or you have larg=
e attachments.
+ Specifying a local `source` database and a remote `target` database is ca=
lled ''push replication'' and a remote `source` and local `target` is calle=
d ''pull replication''. As of CouchDB 0.9, pull replication is a lot more e=
fficient and resistant to errors, and it is suggested that you use pull rep=
lication in most cases, especially if your documents are large or you have =
large attachments.
  =

  =3D=3D=3D Continuous replication =3D=3D=3D
 =20