title: What is lost from the stack when a service handles async messages in ServiceStack?
body: <p>I'm using the messaging feature of ServiceStack for back end transactions I expect to involve database locks where consistency is very important. </p>
  
  <p>I've registered handlers as explained in the documentation: </p>
  
  <pre><code>mqHost.RegisterHandler&lt;Hello&gt;(m =&gt; {
      return this.ServiceController.ExecuteMessage(m);
  });
  </code></pre>
  
  <p>I've noticed the Filters don't get called. Presumably, they're really "Http" filters similar to MVC. So it makes sense they're ignored.</p>
  
  <p>How does Authorization work with message handlers, is it ignored too? </p>
  
  <p>And as I want to keep my async services internal, and always async, is there any benefit in making them inherit from ServiceBase at all?</p>
  
  <p>As I'm thinking of creating another envelop layer between IMessage and Body for some Identity data that can be passed from my public services out of AuthSession and to the Async service.</p>