[
https://issues.apache.org/jira/browse/COUCHDB-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151241#comment-13151241
]
Filipe Manana commented on COUCHDB-1341:
----------------------------------------
Adam, I'm not very keen on using _session.
If between 2 consecutive requests made by the replicator the cookie expires,
then we need extra code to POST to session again and retry the 2nd request,
making it all more complex then it already is. This is much more likely to
happen when retrying a request (due to the sort of exponential retry wait
period), or during continuous replications for longs periods where both source
and target are in sync (no new requests done to the source).
> calculate replication id using only db name in remote case
> ----------------------------------------------------------
>
> Key: COUCHDB-1341
> URL: https://issues.apache.org/jira/browse/COUCHDB-1341
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Reporter: Bob Dionne
> Assignee: Bob Dionne
> Priority: Minor
>
> currently if the source or target in a replication spec contains user/pwd
> information it gets encoded in the id which can cause restarts if the
> password changes. Change it to use just the db name as the local case does,
> Here's a draft[1] of a solution.
> [1] https://github.com/bdionne/couchdb/compare/master...9767-fix-repl-id
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
