[
https://issues.apache.org/jira/browse/COUCHDB-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237967#comment-14237967
]
Robert Newson commented on COUCHDB-2497:
----------------------------------------
I think you miss my point. "persistent":true in the request body to _replicate
would cause us to store that information in a database.
What _replicator is is a regular database that we monitor for changes. It was a
cute idea, but I've administered this idea in production for years and I
absolutely hate it now.
> Deprecate /_replicate endpoint
> ------------------------------
>
> Key: COUCHDB-2497
> URL: https://issues.apache.org/jira/browse/COUCHDB-2497
> Project: CouchDB
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: HTTP Interface, Replication
> Reporter: Alexander Shorin
>
> We have two similar API to run replications. How about to reduce them single
> one? We cannot just return HTTP 301 on /_replicate to /_replicator for POST
> requests since in this case user must confirm the request submission whatever
> that means. But we can just reroute requests internally or try to use
> experimental [HTTP 308|http://tools.ietf.org/html/rfc7238] to deal with it.
> The motivation is the simplification of replication tasks management, since
> it doesn't simply to cancel active temporary replication as like as it could
> be done for persistent ones.
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
