Hi Sander, You wrote:
"Bundling requests is most of the time a good idea. It's a bit more work on the client, but if your app is going to be run on a high-latency network (mostly mobile) it is a big plus for your application." How are you doing this on the client? I have been "bundling" on the server and use one request from the client (using a route resolve to get the data). On Thu, Sep 18, 2014 at 9:08 AM, 'Michael Bielski' via AngularJS <[email protected]> wrote: > FWIW, when I first learned BASIC in high school we did not have screens. It > was all done on teletype-like terminals that saved your program on paper > tape. After that I bought an Atari 800XL and really thought I was stylin! > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
