Is the Dropbox Datastore conflict resolution API just a broken, naive version of operational transformations? https://www.dropbox.com/developers/blog/56/how-the-dropbox-datastore-api-handles-conflicts-part-two-resolving-collisions …
-
-
@bascule I guess my answer to your original question is "no," it's not a broken or naive version of OT. :-) -
@smarx and I guess my response to your approach is "lots of complexity for half the wins you could get out of that approach" -
@bascule I'm still not clear on where there's unnecessary complexity. The protocol is remarkably simple (except lists, which do require OT). -
@smarx you're in the uncanny valley between simpler algorithms and ones which allow you to sync hierarchical data structures -
@bascule We're not dealing with hierarchical data structures, so that's irrelevant. And that's not because we couldn't figure out how. :-) -
@smarx well congrats on shipping something like OT-as-a-service. Many have tried and failed -
@bascule Thanks for that and for the lively discussion. :-) Stop by Dropbox sometime if you want to chat with more of the team. -
@smarx might take you up on that sometime
End of conversation
New conversation -
-
-
@bascule Among other reasons, we "punt" to the client because it will allow for custom resolution rules in the future.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.