{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 ゆ 、 Hurt° 的问题《Castle Windsor: PerThread vs PerWebRequest in ASP.》','https://www.manongdao.com/q-576636.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
A lot of people seem to use the PerWebRequest lifestyle in web apps for managing certain contexts. I have two concerns:
- PerWebRequest has a dependency on an http module (right?).
2. PerWebRequest has a dependency on HttpContext. I have some ASP.NET code that fires off in a separate thread (and loses HttpContext).
It seems that ASP.NET / IIS starts a new thread for each web request. Is there any reason not to just use the PerThread lifestyle and not have to worry about these dependencies? Or is there some advantage to PerWebRequest?