While we're on the subject of Ember, can an ember guru please share some of your wisdom by explaining the following:<p>Q1: When given some instance of DS.Model, how does DS.Store figure out what child-class of DS.Model it is?<p>Q2: Where and how do DS.Model child-classes get registered with the main ember application?<p>Q3: Say you have some model Person = DS.Model.extend(...) and some PersonAdapter = DS.ActiveModelAdapter.extend(...), when does Ember go about and register your PersonAdapter and figuring out it should be used with the Person model?<p>I'm trying to create something very like the DS.Adapter system for Ember, except instead of handling ajax requests for data persistence, it would do data live updates, but I'm confused at exactly how Ember goes about registering its parts.
Another thing: Ember-Data doesn't support PATCH (last I looked) so it requires sending the <i>whole</i> model to save changes. This can have unintended consequences when you only want to update <i>one</i> thing, but have to send <i>every</i>thing.
It's always helpful to see summaries of other people's experiences with platforms. Ember is going through a big growing period right now and feels like a moving target, but it has a strong direction.
Note that ArrayControllers (which are often/always used as part of an "each" loop, and can set via itemController in handlebars, if needed) are not singletons, unlike standard controllers. Very useful for lists of items that need individual control.