title: Bad practice in a single page app to GET from one request and PUT to another and create sub models off a main model?
body: <p>The backend developer has designed the RESTful API in such a way that when going into a section of the site I call one large request for all the data in all the sub sections.  These sub sections data can be modified and saved.  If that happens I would need to create a new model based on the model from the large request, populate it, and save it to a different service (PUT).  This service can only PUT and not GET. I would probably create this model as soon as the user navigated to this section, and display the view based on this new model.  Now if i navigated to another sub section, that large request model would be out of date and I'd have to fetch it from the backend again instead of making a smaller request for that section.  </p>
  
  <p>I propose to him to just create separate services for each sub section that i can easily fetch and save to (I'm using Backbone).  Otherwise I'm creating sub models off a main model and they are dependent on each other and I'd have to write the code to wire them together instead of leveraging the power of the built in methods on the model like save, sync, fetch.</p>
  
  <p>Does this not also create an issue in creating modular components if models are depending on other models?</p>
  
  <p>Has anyone seen it done this way?</p>