Hi Teddy. This is an issue I have also run into using angular. Since the angular paradigm involves downloading all of the layout at the same time, the static content becomes very heavy with large applications. I worked on converting a full page app into angular when the full page app was 400 pages. We had to break the application into pieces and make a bunch of mini apps out of it. We did this from the menu item for each module. The security issue is also a problem because you can end up downloading a bunch of pages that the user has no right to have in their client. It clues hackers in to what they are missing. Not a good think. Have you tried an HTML injection paradigm instead of a JSMVC one? A good example on that is WebRocketX www.webRocketX.com
On Tuesday, December 22, 2015 at 6:10:04 PM UTC-7, Teddy Hartanto wrote: > > Hi, may I ask is it a good practice to break a huge angular app into > multiple page application? For instance, suppose i have an e-commerce > website, the authentication part is handled by one app, and the main > website is handled by another one. > > Is this a good practice? Also, what if i want the main website to be > accessible only after the user has logged in? How do i prevent the user > from accessing the main website if he/she is not authenticated? > > Thank you very much > > -- 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 angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
