couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1824) Official documentation of replication algorithm?
Date Sat, 28 Sep 2013 18:49:05 GMT


Alexander Shorin commented on COUCHDB-1824:

[~benoitc], yea, I saw that, but hadn't figure how to combine it with RFC-style definition.
I really like such style and feels that it more developer friendly than pseudo-code. Probably,
I spend not enough time for this issue.

[~snej], I respect your experience with TouchDB and writing compatible replicator - your protocol
definition looks solid and detailed, but I was fear to blindly copy-past anything from it
by one simple reason: compatible things may be different in details and I was aware that Couchbase
todays is very different from CouchDB unlike it was at his very first days. Probably, I have
to consult with you first - than that's my fault and I'm sorry for that.

Guys, I'm not an expert in this question and, probably, I have to implement replicator by
my own to understand and document all the important bits or at least be able to defend any
points of the definition. But until then please be so kind to transform any critics into patches
- that's would be more productive and helpful for all of us (:

Reopening till we reach some consensus about the replication protocol or till I'm personally
understand how this things works.
> Official documentation of replication algorithm?
> ------------------------------------------------
>                 Key: COUCHDB-1824
>                 URL:
>             Project: CouchDB
>          Issue Type: Documentation
>          Components: Documentation
>            Reporter: Nathan Vander Wilt
>            Assignee: Alexander Shorin
>             Fix For: 1.5.0
> Though it's in some ways an internal detail, it might be nice to provide a canonical
description of CouchDB's replication protocol (algorithm, really) in the documentation. See
links at:

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

View raw message