title: Injecting Current User with Ninject this way - any disadvantages?
body: <p>I'm using this ninject bind:</p>
  
  <pre><code>kernel.Bind&lt;ICurrentUser&gt;().To&lt;CurrentUser&gt;()
      .InRequestScope()
      .WithConstructorArgument("principal", 
          context =&gt; (RolePrincipal HttpContext.Current.User);
  </code></pre>
  
  <p>In one of my decorators of the service layer I simply add "ICurrentUser currentUser" to the constructor to get the object and its working.</p>
  
  <p>Are there any disadvantages by this implementation or is there a better way to implement his ambient context? For each request the user object is created - also if its an anonymous user.</p>