apologies, just a correction. The security concern is that the database
might contain data which should be NOT visible/accessible to all the
clients.
On Wed, 2013-12-11 at 16:22 +0100, Apostolos Emmanouilidis wrote:
+1 for starting with an implementation similar to CouchDB. This
looks
like the Offline Lock pattern where there are version stamps and a
client cannot fulfill a transaction if he has an old current version
stamp.
Regarding the concepts that Summers sent
https://neil.fraser.name/writing/sync/ I feel that are some Open Source
implementations of these concepts out there.
e.g google-diff-match-patch[1]
And something more, there is a security parameter in the data sync
concept. The database might contain data which should be
visible/accessible to all the clients.
[1]:
https://code.google.com/p/google-diff-match-patch/
On Wed, 2013-12-11 at 10:37 +0100, Daniel Bevenius wrote:
> This conflict would the have to be handled by the client. Could we
> start out with something similar and as simple as this and evolve it?
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev