为什么我们告诉AppDomains不提供错误隔离? [英] Why are we told AppDomains provide error isolation when they don't?
问题描述
我最近做了一些实验，以了解如何使用AppDomian在我们这里具有高性能的异步服务器中隔离服务器会话.
I did a few experiments recently to get the feel for how to use AppDomian to isolat server sessions in a high-perf async server we have here.
我发现在创建的应用程序域中发生未处理的异常会杀死整个过程，这与我在无数书籍和文章中所读的内容完全相反.
What I found was that an unhandled exception in a created app domain, kills whole process, the very opposite of what I have read in countless books and articles.
然后我发现许多网络文章说它们曾经在.Net 1.1中有效，但是从.Net 2开始就没有了.
I then found hosts of web articles saying that this used to work in .Net 1.1, but ever since .Net 2 it doesnt.
我想念什么吗?
Cap'n
推荐答案
Have you read these (http://stackoverflow.com/questions/7071957/appdomain-handling-the-exceptions) and (http://stackoverflow.com/questions/5078209/why-does-a-stackoverflowexception-in-a-child-appdomain-terminate-the-parent-appd)? Pretty much similar scenario. I've tried AppDomain with assemblies and it does survive, when 1 assembly gets crashed. Need to check with threads though.
这篇关于为什么我们告诉AppDomains不提供错误隔离?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
