couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1341) calculate replication id using only db name in remote case
Date Wed, 16 Nov 2011 14:50:51 GMT


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:
>             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]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message