Skip to content
This repository has been archived by the owner. It is now read-only.

Implement Replication layer #417

yaronyg opened this issue Jan 7, 2016 · 2 comments

Implement Replication layer #417

yaronyg opened this issue Jan 7, 2016 · 2 comments


Copy link

yaronyg commented Jan 7, 2016

Depends on #317

@yaronyg yaronyg added this to the New Infra milestone Jan 11, 2016
@yaronyg yaronyg self-assigned this Jan 25, 2016
Copy link
Member Author

yaronyg commented Jan 25, 2016


  • Look in _Local/<peerID> to find the last sync sequence numbers for the people on our lookup list
  • Set timer to check for changes to the DB
  • Put logic in timer to check if beacons have expired
  • Add in distinction between foreground and background update rates
  • Limit the number of peers we notify
  • Generate Notification beacons



  • Figure out how to properly handle setting the sequence we have updated to
  • Set logic to send an update based on a change event but rate limited based on the pushLastSyncUpdateMilliseconds value
  • Set our change watcher to make sure we kill a connection once no useful work is happening
  • Set up the actual replication
  • Handle all the events off the replication
  • Figure out how to translate the replication errors into the smaller set of errors that start is
    supposed to return to the peer pool manager
  • Support kill properly
  • Figure out why testThaliReplicationPeerAction doesn't exit at the end

Copy link
Member Author

yaronyg commented Jun 24, 2016

This work is done. I'm just blocked on pouchdb/pouchdb#5114 which I have a proposed resolution to and pouchdb/express-pouchdb#329 which I can't check in until we get the build system for express-pouchdb back up and running.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

1 participant