title: Search results filter - controller or service or filter?
body: <p>I have a search results page. The search results page is basically one large controller at the moment. I have code which is for the filters however this isn't an angularjs filter as such because I'm making another search to back-end and I'm not just returning a different array set. I want to keep the filter separete from the search results controller because its already large as it is. My question is: do I make it another controller and broadcast changes to the searchResults controller or do I make it a service or is it actually a filter? </p>
  
  <p>I'm currently thinking a separete controller makes more sense as I'm still having to use scope but with a service I can only use $rootScope it seems.</p>
  
  <p>Overall it would be good to know what calls for a filter and controller. </p>