Ember.js Persistence Foundation
1–10 of 23 posts
Re: Ember.js Persistence Foundation
#2This is super cool - What method is used for continued client side updates? Websockets, polling?
Re: Ember.js Persistence Foundation
#3> Epf is essentially an ORM for the web and gives you all the tools necessary to define models and synchronize with your backend.
That line should be on the front page of that website. I've spent too much time trying to decipher the bizarre diagram and trying to figure out whether it was an inside joke I wasn't getting or an actual thing.
Re: Ember.js Persistence Foundation
#4Now if this works, which Ember-data doesn't (not finished I guess). This is a bigger step towards using Ember,
Re: Ember.js Persistence Foundation
#5> Epf is essentially an ORM for the web and gives you all the tools necessary to define models and synchronize with your backend. That line should be on the front page of that website. I've spent too much time trying to decipher the bizarre diagram and trying to figure out whether it was an inside joke I wasn't getting or an actual thing.
THIS! That diagram is just ...
Re: Ember.js Persistence Foundation
#6This is super cool - What method is used for continued client side updates? Websockets, polling?
The readme says it works with any "persistent backend such as a REST API or socket connection".
It looks like it tries to be backend-agnostic, and do the sync work on the client side.
Re: Ember.js Persistence Foundation
#7This is super cool - What method is used for continued client side updates? Websockets, polling?
The readme says it works with any "persistent backend such as a REST API or socket connection". It looks like it tries to be backend-agnostic, and do the sync work on the client side.
I'm assuming - and this could be a bad assumption - but based on the continuing updates architecture, if client a changes model a, client b will see an update on model a. How does client b get notified of the change? Does it have some kind of fallback system ala socket.io? Is this not yet part of the project?
Re: Ember.js Persistence Foundation
#8> Epf is essentially an ORM for the web and gives you all the tools necessary to define models and synchronize with your backend. That line should be on the front page of that website. I've spent too much time trying to decipher the bizarre diagram and trying to figure out whether it was an inside joke I wasn't getting or an actual thing.
THIS! That diagram is just ...
The diagram is horrible and doesn't really explain anything. I want to know what it is, not stare at some cryptic diagram for ten minutes.
Re: Ember.js Persistence Foundation
#9Now if this works, which Ember-data doesn't (not finished I guess). This is a bigger step towards using Ember,
I've been using Ember-data for the past few months on side projects and it's getting a lot more stable. I've rarely had issues with it in the past few weeks.
Re: Ember.js Persistence Foundation
#10Earlier quoted context omitted.
The readme says it works with any "persistent backend such as a REST API or socket connection". It looks like it tries to be backend-agnostic, and do the sync work on the client side.
I'm assuming - and this could be a bad assumption - but based on the continuing updates architecture, if client a changes model a, client b will see an update on model a. How does client b get notified of the change? Does it have some kind of fallback system ala socket.io? Is this not yet part of the project?
Backbone took a REST opinion, I imagine if you want something like you describe, they (or someone) will implement something like backbone.io.