couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2497) Deprecate /_replicate endpoint
Date Mon, 08 Dec 2014 16:25:13 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238019#comment-14238019
] 

Alexander Shorin commented on COUCHDB-2497:
-------------------------------------------

Yes, it seems I did. But thanks for clarification, I think I got the idea and why it wouldn't
work. Probably, for my motivation enhancing /_active_tasks might be more better way to go,
but that's another story.

> 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)

Mime
View raw message