Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08CB61082F for ; Mon, 8 Dec 2014 15:24:13 +0000 (UTC) Received: (qmail 82962 invoked by uid 500); 8 Dec 2014 15:24:12 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 82899 invoked by uid 500); 8 Dec 2014 15:24:12 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 82876 invoked by uid 99); 8 Dec 2014 15:24:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 15:24:12 +0000 Date: Mon, 8 Dec 2014 15:24:12 +0000 (UTC) From: "Robert Newson (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COUCHDB-2497) Deprecate /_replicate endpoint MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)