flimzy commented on a change in pull request #349: More information about replication. Fixes #346 URL: https://github.com/apache/couchdb-documentation/pull/349#discussion_r232980361
########## File path: src/replication/intro.rst ########## @@ -26,18 +26,46 @@ the end of the process, all active documents on the source database are also in the destination database and all documents that were deleted in the source databases are also deleted on the destination database (if they even existed). -Triggering Replication -====================== -Replication is controlled through documents in the -:ref:`_replicator <replicator>` database, where each document describes one -replication process (see :ref:`replication-settings`). +Transient and Persistant Replication +==================================== + +There are two different kinds of setting up a replication. The first one that was +introduced into CouchDB leads do a replication that could be called `trancient`. +Trancient means that there are no documents backing up the replication. So after a +restart of the CouchDB server the replication will disapear. Later in time the +:ref:`_replicator <replicator>` database was introduced which keeps documents +containing your replication parameter. Such a replication can be called `persisent`. +Trancient and persistent replications can have different Review comment: Spelling correction: ```suggestion Transient and persistent replications can have different ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
