title: Should service layer have access to HttpContext?
body: <p>I'm building an application that roughly follows the repository pattern with a service layer on top, similar to early versions of Conery's MVC Storefront.</p>
  
  <p>I need to implement a page that returns all users except for the current user. I already have GetUsers() methods on the repository and service layers, so the question is where to apply the "except for the current user."</p>
  
  <p>Should the service layer be aware of HttpContext, thus applying this rule?  I am tempted to just pass in the current user (id) from the controller to this service method, but it seems cleaner if the service layer was HttpContext-aware and could do this on its own. </p>
  
  <p>One obvious alternative is to apply this rule directly within the Controller, but I'm just not hot on that idea...</p>
  
  <hr>
  
  <p>Edit - just to comment on the answers:  I see the issues with the reverse dependency problem, something I was completely overlooking. I'm marking Mehrdad's as the answer due votes, but everyone has really provided a valuable response worth reading!</p>