Consider using HTTP request based lifetime scopes in SignalR, much like MVC

[GoogleCodeExporter]

https://github.com/bytenik/Autofac.Integration.Mvc.SignalR

If you do not like the SignalR dependency on the MVC library, consider 
abstracting the HTTP components from the MVC library into a core HTTP assembly 
and referencing it from both.

Original issue reported on code.google.com by byte...@bytenik.com on 3 Feb 2013 at 1:56

[GoogleCodeExporter]

Thanks for the link. I will take a look.

Original comment by alex.meyergleaves on 3 Feb 2013 at 11:09

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by alex.meyergleaves on 3 Feb 2013 at 11:11

[GoogleCodeExporter]

After submitting this, I realized that you don't have access to 
HttpContext.Current from within SignalR; I'm going to speak with the SignalR 
team tomorrow to see how we can resolve this.

Original comment by byte...@bytenik.com on 3 Feb 2013 at 11:12

[GoogleCodeExporter]

I tried storing the lifetime scope into CallContext instead of HttpContext, but 
the end result is the HTTP module disposes the scope prior to SignalR 
completing the request.

Original comment by byte...@bytenik.com on 3 Feb 2013 at 11:14

[GoogleCodeExporter]

Original comment by travis.illig on 12 Feb 2013 at 5:41

• Added labels: Module-Integration-SignalR

[GoogleCodeExporter]

I spoke with David Fowler about this and it's simply not possible in the 
current implementation of SignalR. I'll leave this item here for a while as a 
reminder to check up on new releases and hassle David some more.

Original comment by alex.meyergleaves on 2 Jul 2013 at 12:21

[GoogleCodeExporter]

Moved issue to GitHub: https://github.com/autofac/Autofac/issues/403

Subsequent issue management will be held there; closing the issue on Google 
Code as "WontFix" because we will handle issue resolution on GitHub.

Original comment by travis.illig on 11 Feb 2014 at 12:04

• Changed state: WontFix