Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • This doesn't answer my question. It just criticizes my use of the word "generate" and tells me what AngularJS does. The question is: how do I avoid two requests to the server? Commented Jan 15, 2014 at 3:08
  • The criticism comes from, as recommended by Backbone, Angular, Jquery, and many other libraries, the skeleton of your application should be static with libraries, templates, it should be made ​​available in a distributed environment (maybe a CDN). So in my opinion, in a MV* context, the first response from the server 1) does not generate HTML, 2) does not generate load in your application. Commented Jan 15, 2014 at 7:04
  • I'm not disagreeing with what you are saying. But generating a skeleton (which is HTML) does require work on the server unless it is truly static and cache-able. Browsers have limitations on the number of concurrent requests. I was curious whether there was a way to eliminate one of the first hits. Templates have the benefit of being truly static and therefore are cached. Those don't concern me as much as the dynamic content - the skeleton and the API data. @zachary-k answers my question and now I am just hoping for other possible approaches. Commented Jan 15, 2014 at 12:37