Sorry for taking a while to look at this, busy with couchdb conf etc In general I agree with Jens, this serves as great documentation for how CouchDB's replication works, but its very detailed without a high level overview
The PouchDB replicator was done following what Jens documented @ https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithmwhich was invaluable Another problem is that its difficult to distinguish between an implementation and a spec, a session id isnt needed for a pull replication, revs diffs arent always needed, the details around the HTTP semantics (especially the multipart/mixed) stuff is not relevant to PouchDB as Jens mentioned, things like ensure_full_commit are quite specific I think one major improvement would be to restore the original high level documentation (as seen @ https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithm or http://dataprotocols.org/couchdb-replication/) and use the current detailed sections as additional references As it is, one problem I can see would be: 4.2.4.1. Verify Peers would suggest that its impossible to do pull replication if you dont have write permissions on the database, I am not sure if thats because I am havig a hard time following the diagram or thats what it is actually saying Thanks a lot for this work On 12 November 2013 06:21, Alexander Shorin <[email protected]> wrote: > On Tue, Nov 12, 2013 at 9:35 AM, Benoit Chesneau <[email protected]> > wrote: > > On Tuesday, November 12, 2013, Alexander Shorin wrote: > >> https://github.com/kxepal/couchdb-replication-protocol > > > > hrmmm why another repo? i have created the hacking repo on my github for > > that... Or we can like we said put all in a couchdb branch and > collaborate > > via git/github. At least i thought we decided that... > > Errr...that was unwise step from my side. Moved to CouchDB feature > branch. Sorry! > > > will review in another mail. > > > > - benoƮt > > Thanks! > > -- > ,,,^..^,,, >
