title: Sling resource.getResourceResolver() Vs SlingHttpRequest.getResourceResolver
body: <p>In my project I am seeing in Sling model classes, the resource resolver is fetched in 2 ways</p>
  
  <pre><code>@Inject private Resource resource;
  ResourceResolver resolver = resource.getResourceResolver();
  </code></pre>
  
  <p>Vs</p>
  
  <pre><code>@Inject @Self private SlingHttpServletRequest request;
  ResourceResolver resolver = request.getResourceResolver();
  </code></pre>
  
  <p>While both are Sling implementations, is there any benefit of using one opposed other? Or are these 2 yield same resolver with no performance difference?</p>