Any real world cases for this? >>> >>> Use case: >>> 1. I get a subset of the data for field work for a couple of days. >>> Coming back from field work, I "sync" the edits to the main data >>> server. An application takes care of the merge like git does. >>> >>> 2. Two field workers, edit the same data on a different area. An >>> application manages the conflict before merging to main data server. >>> >>> >> >> Hi, >> >> for the sync part you should have a look at CouchDB [1]. Though it doesn't >> do the hard part of resolving conflicts. This part would need to be coded. >> >> [1] http://couchdb.apache.org/ >> >> Cheers, >> Volker >> _______________________________________________ >> Discuss mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/discuss > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/discuss >
-- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------ _______________________________________________ Discuss mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/discuss
