Is this supposed to be a framework for collaborative editing and synchronization? I would expect a lot more examples around merge conflicts and locking if so. "Models are never locked" make this sound like it is just an abstraction for abstraction's sake, why would I use this instead of just binding DOM elements to JSON?
Ember.js Persistence Foundation
21–23 of 23 posts
Re: Ember.js Persistence Foundation
#22Earlier quoted context omitted.
Don't want to show off, but it seemed quite readable to me, once you notice that the arrows have numbers.. It shows many interesting details (the only API command seems to be Patch. There are two sync phases on the client, one to determine what to send to the server, one to determine what to merge upon server response). I quite like diagrams :))
What do the numbers represent?
Lifecycle of data as it changes, apparently.
Re: Ember.js Persistence Foundation
#23Is this supposed to be a framework for collaborative editing and synchronization? I would expect a lot more examples around merge conflicts and locking if so. "Models are never locked" make this sound like it is just an abstraction for abstraction's sake, why would I use this instead of just binding DOM elements to JSON?
It's made to be a generic ODM/ORM for use on the client side with Ember.js. It's a replacement for Ember Data, which has a ton of bugs and limitations.