I’m embarking on my first AngularJS application and had a few questions on how I was planning to build this application.
Would it be considered bad Angular application design by having each page basically being it's own angular application? In this structure the server-side framework would control the routing, user authentication & authorization. Each view in this application would contain it’s own ng-app. While there would be page refresh inbetween pages, but all actions on an individual page would be controlled by Angular. Would this type of application structure be a bad idea? Any pros and cons I should be aware of in this application structure? Or should I strive for the true single page app and leaving the server-side frameworks only do the API. I would greatly appreciate any opinions, resources or feedback on this topic. I just want to make sure I'm making the right architecture decisions for my application. Thanks, bnewton -- 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.
