In my web application, I have two models: Domain and URI. A domain has many URIs and an URI belongs to a domain. A domain can have more than a thousand URIs. That’s why I can’t just put all the URI ids in the domain object an declare the URIs property of a domain as async. In addition, I can’t return all the URIs of a domain in one api call, I must have a pagination for this ressource.
I’m pretty surprised to reach the REST adapter limitations with such a trivial REST api.
Moreover, what’s about garbage collection? If I do implement an adapter that deals with my first problem, does ember-data will keep all the loaded records even if they are not used anymore?
What is the best practice to deal with this in Ember?