For each request processed by the ASP.NET engine, each configured HTTP module is initialized and allowed to wire up event handlers to the events raised during the processing of the request.
对于由asp.net引擎处理的每个请求，将初始化每个已配置的HTTP模块，并允许将事件处理程序绑定到处理请求期间所引发的事件。
Our async HTTP engine has also be reused in our async HTTP client, so we can now scalable produce request and consume responses.
我们的异步http客户端重用了异步http引擎，这样就能以可伸缩的方式生成请求并处理响应了。
The stress tool is a simple, high-performance, threaded HTTP engine that simulates a very heavy load of HTTP clients.
压力工具是一个简单的、高性能的、使用线程的HTTP引擎，它模拟高强度压力的 HTTP 客户负载。
After initializing the appropriate HTTP modules, the ASP.NET engine determines what HTTP handler or HTTP handler factory to invoke for the given request.
初始化相应的HTTP模块后，ASP.NET引擎将确定为给定的请求调用哪个HTTP处理程序或HTTP处理程序工厂。
For example, an HTTP 1.1 connector can work with an SSL connector on the same engine.
例如，HTTP 1.1连接器可以在同一引擎上与SSL连接器一起工作。
In a similar vein, ASP.NET provides HTTP modules that can respond to the events raised by the ASP.NET engine.
同样，ASP.NET提供了HTTP模块，该模块可以响应由asp.net引擎引发的事件。
In our case, however, you want to isolate the engine scopes and the output of the scripts running in different threads, which means you must create a new ScriptContext instance for each HTTP request.
不过，在本例中，我们想要隔离这些引擎范围以及运行在不同线程内的那些脚本的输出，这意味着必须要针对每个HTTP请求创建一个新的ScriptContext实例。
A flexible rule engine sits in the heart of ModSecurity. It implements the ModSecurity rule language, which is a specialised programming language designed to work with HTTP transaction data.
灵活的规则引擎是ModSecurity的核心，其实现了ModSecurity的规则语言，这是一个专用的程序语言设计的用于处理HTTP的传输数据。
The RESTChess team build an engine to map exceptions to appropriate HTTP error codes.
RESTChess团队构建了一个引擎，能够将异常映射到适当的HTTP错误代码。
Next, the ASP.NET engine initializes the configured HTTP modules.
接下来，ASP.NET引擎对已配置的HTTP模块进行初始化。
The difference in this case are: there is only a single web-facing HTTP binding component and there are two different BPEL service engine components that each implement the same service (epB.)
这个示例中的不同点在于：这里只有一个面向Web的HTTP绑定组件和两个不同的BPEL服务引擎组件，每个引擎组件执行相同的服务（epB）。
The difference in this case are: there is only a single web-facing HTTP binding component and there are two different BPEL service engine components that each implement the same service (epB.)
这个示例中的不同点在于：这里只有一个面向Web的HTTP绑定组件和两个不同的BPEL服务引擎组件，每个引擎组件执行相同的服务（epB）。
应用推荐