5

I have a ServiceStack API application which uses Simple Injector as its IoC container. I need certain components to have a 'per web request' lifestyle.

I looked up in the Simple Injector documentation here, and found that it has not one, but two lifestyles corresponding to 'per web request':

  1. Per Web Request
  2. Per Web API Request

This confused the hell out of me because I always thought all ASP.NET applications used the same basic pipeline, and that IoC containers implemented per web request by plugging in an HTTP module. Why would this be different for Web API applications?

Can anyone shed some light about which is most appropriate for a ServiceStack API application?

Steven
  • 166,672
  • 24
  • 332
  • 435
David
  • 15,750
  • 22
  • 90
  • 150
  • 2
    Out of curiosity, why not use the ServiceStack Funq IoC? – Scott Mar 05 '14 at 11:19
  • @Scott: Probably because he needs one of the features that Func lacks, such as [registration of open-generic types](https://simpleinjector.codeplex.com/wikipage?title=Advanced-scenarios#Registration-Of-Open-Generic-Types) or [registering decorators](https://simpleinjector.codeplex.com/wikipage?title=Advanced-scenarios#Decorators). – Steven Mar 05 '14 at 11:31
  • @Scott: I'm afraid the answer is I don't know! I didn't set up the IoC for the application. – David Mar 05 '14 at 11:56
  • Take a look at this answer: https://stackoverflow.com/questions/22242239/simpleinjector-registerwebapirequest-vs-registerperwebrequest. It is better and more accurate than my answer. – Steven Mar 07 '14 at 09:10

1 Answers1

5

The Per Web Request is actually a 'Per HttpContext Request', and under the cover it caches instances using the HttpContext.Current.Items dictionary. This model however starts to break down quickly when you're using Web API, which is caused by the asynchronous model of Web API and the fact that Web API applications can run in a self-hosted environment (which means: no there's no HttpContext.Current at all).

That's why Simple Injector provides a specific lifestyle for Web API applications. This Per Web API Request lifestyle uses the new Execution Context Scope in the background which allows flowing the scope with asynchronous methods.

Can anyone shed some light about which is most appropriate for a ServiceStack API application?

If ServiceStack is asynchronous in nature or is self-hosted, you're better of with the WebApiRequestLifestyle or the ExecutionContextScopeLifestyle. If there's always a HttpRequest.Current when running inside ServiceStack you can use the WebRequestLifestyle.

Community
  • 1
  • 1
Steven
  • 166,672
  • 24
  • 332
  • 435