In regards to your problem, Michael, I think you'll do fine with services. You can get really fancy with them if you want to. A number of mine contain type definitions, factory methods, and numerous injected dependencies of their own.
I think that Rachel left a lot unsaid about why "composing" with multiple controllers is better than using services, but it sounded like she needed: - Multiple instances of the object type, whereas services only allow one instance - Dependency injection into the individual instances Beyond that, we're left guessing. My wager: they ran into a very specific problem, and chose a clever "experimental" solution, in part just to see how it would turn out. Sounds fun! But while it's clever idea, from the outset it sounds like a pretty tangled and confusing way to do things. New controllers will create new inherited scopes, which might become difficult to keep straight. If they are not handled carefully, they will cause performance problems. (This further leads me to wonder: why weren't they just using directives?) -- 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.
