i wonder what are the pitfalls of not adapting it, as i am facing many problems with integrated mode. for example URLRewritng.net is not parsing Arabic query string with integrated mode, plus many other problems.
我想知道不适应它的缺陷是什么,因为我面临着集成模式的许多问题。例如,URLRewritng.net没有使用集成模式解析阿拉伯语查询字符串,还有许多其他问题。
better yet question that is their ability to combine both from web.config, i mean let some HTTP handlers and modules function in mode that suits it ?
更好的问题是他们从web.config中结合两者的能力,我的意思是让一些HTTP处理程序和模块以适合它的模式运行?
1 个解决方案
#1
The main advantage with IIS7's integrated mode seems to be native .NET integration into the HTTP request/response pipeline.
IIS7集成模式的主要优势似乎是将本机.NET集成到HTTP请求/响应管道中。
Native integration gives you access to each and every request, even for static files, and requires no configuration on the server itself just a setting in the configuration file, something which makes shared hosting easier.
本机集成使您可以访问每个请求,甚至是静态文件,并且不需要在服务器本身上配置配置文件中的设置,这使得共享主机更容易。
In IIS6 it was possible to integrate .NET into the pipeline by using a wildcard mapping (*) which basically gave you most of the advantages of IIS7 Integrated Mode, even though it's been said that wildcard mapping degrades performance, no one seemed to have specific numbers and this SO question actually shows that performance is not impacted at all.
在IIS6中,可以通过使用通配符映射(*)将.NET集成到管道中,这基本上为您提供了IIS7集成模式的大部分优势,尽管有人说通配符映射会降低性能,但似乎没有任何特定的数字和这个问题实际上表明性能根本没有受到影响。
I don't think it's worth the effort to change your code just to support Integrated Mode, stick to Classic Mode and turn on wildcard mapping if necessary.
我不认为为了支持集成模式而改变代码是值得的,坚持经典模式并在必要时打开通配符映射。
#1
The main advantage with IIS7's integrated mode seems to be native .NET integration into the HTTP request/response pipeline.
IIS7集成模式的主要优势似乎是将本机.NET集成到HTTP请求/响应管道中。
Native integration gives you access to each and every request, even for static files, and requires no configuration on the server itself just a setting in the configuration file, something which makes shared hosting easier.
本机集成使您可以访问每个请求,甚至是静态文件,并且不需要在服务器本身上配置配置文件中的设置,这使得共享主机更容易。
In IIS6 it was possible to integrate .NET into the pipeline by using a wildcard mapping (*) which basically gave you most of the advantages of IIS7 Integrated Mode, even though it's been said that wildcard mapping degrades performance, no one seemed to have specific numbers and this SO question actually shows that performance is not impacted at all.
在IIS6中,可以通过使用通配符映射(*)将.NET集成到管道中,这基本上为您提供了IIS7集成模式的大部分优势,尽管有人说通配符映射会降低性能,但似乎没有任何特定的数字和这个问题实际上表明性能根本没有受到影响。
I don't think it's worth the effort to change your code just to support Integrated Mode, stick to Classic Mode and turn on wildcard mapping if necessary.
我不认为为了支持集成模式而改变代码是值得的,坚持经典模式并在必要时打开通配符映射。