Re:Two Open-source Emails a Day for Five and a Half Years
by jdpage on Tuesday July 09, 2013 @11:52PM
(#6017353)
An operation-based synchronizer is a synchronizer which sends just the changes (the "operations") to the server, rather than the whole new state. So if I add a line of text to something, then it would send back a message to the server saying "this line of text was added".
Presumably, a state-based synchronizer sends the entire updated state every time, but I don't know offhand.
Re:Two Open-source Emails a Day for Five and a Half Years
by lenidot on Wednesday July 10, 2013 @02:29AM
(#6017825)
See slide #5 onwards of:
http://www.cis.upenn.edu/~bcpierce/papers/harmonyslides-2003...
It explains the terms and explores the pros and cons of each approach.
Re:Two Open-source Emails a Day for Five and a Half Years
by Bockit on Tuesday July 09, 2013 @11:44PM
(#6017331)
If I were to guess, I'd say operation based synchronisation is based on syncing user actions and then executing them on the other side to catch up. E.g., user deleted record 23. User added a record with this data. User changed this field to be this new value.
Is it that they only sync with a button push or something and you fetch stuff when content changes on server ?