I wouldn't normally resurrect an old thread but I would like to know if anyone has some thoughts on the above two approaches. In particular in an concerned with the consequences for build plans with creating a new child container per request.
What is the overhead of having to create new build plans for each "per request" item vs retrieving from the HttpContext.Items hashtable ?
Will new build plans have to be created for items resolved from the parent container via the child container ?
As I'm not a fan of the service locator (anti) pattern, where do you store the child container ? The controller factory has to know about this somehow but it is application scope.
How reliable is accessing the HttpContext.Items entries in EndRequest to disposable any applicable objects ?