Stephen, Here is what worked best for me.
Because functionality on the login page is radically different from functionality in my SPA views, I opted to just use different pages entirely for login, registration, etc. I know this is sort of a non-answer, but it eschewed a lot of complexity in my module setup. Also, those pages are very small, so SPA's benefits are, to some degree, lessened anyway. This approach made even more sense in my case, because a great deal of the site's functionality depended on a "User" object -- which contained permission flags for different views and actions, among other things -- which would not be available without an active session. Best, SS -- 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.
