make pairing program update couchdb
Bug #397663 reported by
Chad Miller
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
desktopcouch |
Fix Released
|
High
|
Chad Miller |
Bug Description
The pairing program does nothing so far. Once the inter-couch communication is worked out, poke some data and auth information into the database so it can replicate with paired systems.
For auth, it will almost certainly be OAuth. This will be a unique token per replication target, and the official U1 synch mechanism will be the same as for other nearby paired systems. We're egalitarian that way. U1 is not special.
Along with the OAuth token, there should be some mnemonic information about the pairing so the user can manage replication months or years later and not be confused.
Changed in desktopcouch: | |
assignee: | nobody → Chad MILLER (cmiller) |
tags: | added: story-0169 |
tags: | added: cmiller-k-alpha6 |
Changed in desktopcouch: | |
milestone: | w19-karmic-alpha5 → w21-karmic-alpha6 |
Changed in desktopcouch: | |
status: | Triaged → Fix Committed |
Changed in desktopcouch: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I believe the snapshot of couchdb that is packaged now has what we need in order to replicate.