Per request scopes in e.g. Autofac will eat resources

Sample here: https://gist.github.com/danielwertheim/887868c17ab8cd67be44

Kind of followed your sample code… Probably have missed something. And yes, I know I could inject Func<SomeDependency> instead and have the handler resolve and dispose…

But how do I acomplish per-routed message scoped handlers? If not possible with MediatR, perhaps state that clearly in the sample?

[leddt]

@kappy I see!

I wonder if this can work with Owin? The challenge with Owin is that there is not really a static way of getting the current request context. I’ll have to think about it 😄

[khellang]

So the Q is how to achieve this with MediatR in e.g. something like a long running windows service?

Just resolve the stuff you need from a lifetime scope (as shown in the blog post mentioned)? Make sure you dispose it when you’re finished. Or just dispose the container when you’re done with it.

As you would need to get hooked into before and after the func for resolving the handler…

I’m not sure what you’re talking about here. What func?

Just raising my voice as this easily could lead to people getting more and more handler resources that in turn has resources on … …

I don’t think anyone here are experts on all the containers in the samples that have been contributed to this repo, and by all means, they could absolutely have bugs. I guess it’s generally expected to know how the container you’re using works. That should probably be a requirement anyway - whether you’re using MediatR or not 😉 If you’re having trouble wiring up the container properly, maybe it’s best to just go “pure DI”-style? 😄

If you’re looking to learn more about Autofac and its lifetime scoping and transient tracking, I suggest you read NIck’s blog, specifically An Autofac lifetime primer. There are also some good resources on Controlling Scope and Lifetime in the Autofac docs, specifically the bits about Disposal.