On Sun, Jul 31, 2011 at 12:58, Simon Slavin <slav...@bigfraud.org> wrote:
These two go together. Multi-master replication (one example of which is a > document store) is relatively easy. Datestamp every value (document) and > whichever one has the lastest date is the one you want. > This is perhaps an acceptable answer if everything is bottlenecked on a single centralized server or a cluster of central servers where the notion of time is tightly synchronized. It falls apart badly in a highly distributed environment where ... 1: The clocks on various devices (PCs, laptops, tablets, mobile) are often in error by minutes or even hours. (If, for example, that the system time zone is set incorrectly.) 2: (As Dustin pointed out earlier) You can't know that the user of a mobile device has actually seen the latest edits made elsewhere. (There might not be network connectivity between a particular device and the rest of the network, for example.) -Eric -- Eric Scouten :: software developer, photographer :: Poulsbo, WA (near Seattle) http://ericscouten.com :: click for Flickr, Facebook, Twitter, LinkedIn links _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
