Thats what they did, a controller is a special kind of service that you can bind you - Also, each time you request a controller - you get a new one - while each time you request a service you get the same one.
On Mon, Sep 15, 2014 at 4:49 PM, Ben Rethmeier <[email protected]> wrote: > > Thanks for all the feedback\thoughts. Glad I'm on the right track, but now > I'm starting to wonder couldn't services and controllers, be the same > thing? I mean if services could depend upon each other (which I think they > can right?) and if you could bind to a service (which I think you can't > correct?) Couldn't they be one thing? (If they added the ability to make a > service bind-able maybe give it a different name also) I could just build > my services, then build a new service that depends on the ones that I need > for the view context I want and bind to it, that seems like it would have > been simpler to my mind, anyway just a thought. > > -- > 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. > -- Regards, Ganaraj P R -- 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.
