search

TeensyPass / teensycli

GNU General Public License v2.0
1 stars 2 forks source link

Syncronization #9

Open mvcisback opened 11 years ago

mvcisback commented 11 years ago

A synchronization system should be kept in mind as we develop this code.

I'm not quite sure the best way to go about this. (rsync, dropbox, and bittorrent come to mind)

wkennington commented 11 years ago

The easiest way to avoid the need for a locking system is to keep multiple versions of the password store around and name them based on their data hash or something equivalent. Nodes will merge the files over time and should converge if they keep attempting to merge the data sets.

I don't know how well conflict resolution would work without accurate clocks, but we may have to assume this is true for the most part.

I actually think we should push syncing into the lowest possible layer(storage handler) with callbacks to higher layers where necessary for operations like merging.