title: Passing current scope to an AngularJS Service
body: <p>Is it correct to pass the "current" <code>$scope</code> to an AngularJS service?</p>
  
  <p>I'm in the situation where I've a $service knowing it's consumed by only one controller, and I'd like to have a reference to the controller's scope in the $service methods themselves.</p>
  
  <p>Is this <em>philosophically</em> correct?</p>
  
  <p>Or I'd better to broadcast events to the $rootScope and then make my controller listen to them?</p>