|
|
- ASP.NET Process Model之一：IIS 和 ASP.NET ISAPI
- ASP.NET Process Model之二：ASP.NET Http Runtime Pipeline[上篇]
- ASP.NET Process Model之二：ASP.NET Http Runtime Pipeline[下篇]
現(xiàn)在我們真正進入ASP.NET管轄的范疇，下圖基本上囊括整個處理過程涉及的對象，接下來我們一起來討論這一系列的對象如何相互協(xié)作去處理Http Request，并最終生成我們所需的Http Response。
HttpContext
上面我們介紹了ISAPI在調(diào)用ISAPIRuntime的時候?qū)?yīng)的ISAPI ECB Pointer作為參數(shù)傳遞給了ProcessRequest方法，這個ECB pointer可以看成是托管環(huán)境和非托管環(huán)境進行數(shù)據(jù)交換的唯一通道，Server Variable和Request Parameter通過它傳入ASP.NET作為進一步處理的依據(jù)，ASP.NET最后生成的Response通過它傳遞給ISAPI，并進一步傳遞給IIS最終返回到Client端。
借助這個傳進來的ECB Pointer，我們創(chuàng)建了一個ISAPIWorkerRequest。ISAPIWorkerRequest作為參數(shù)傳入HttpRuntime.ProcessRequestNoDemand的調(diào)用。HttpRuntime.ProcessRequestNoDemand最終體現(xiàn)在調(diào)用ProcessRequestInternal。下面是真?zhèn)€方法的實現(xiàn)：
ProcessRequestInternal
private void ProcessRequestInternal(HttpWorkerRequest wr)
{
HttpContext context;
try
{
context = new HttpContext(wr, false);
}
catch
{
wr.SendStatus(400, "Bad Request");
wr.SendKnownResponseHeader(12, "text/html; charset=utf-8");
byte[] bytes = Encoding.ASCII.GetBytes("<html><body>Bad Request</body></html>");
wr.SendResponseFromMemory(bytes, bytes.Length);
wr.FlushResponse(true);
wr.EndOfRequest();
return;
}
wr.SetEndOfSendNotification(this._asyncEndOfSendCallback, context);
Interlocked.Increment(ref this._activeRequestCount);
HostingEnvironment.IncrementBusyCount();
try
{
try
{
this.EnsureFirstRequestInit(context);
}
catch
{
if (!context.Request.IsDebuggingRequest)
{
throw;
}
}
context.Response.InitResponseWriter();
IHttpHandler applicationInstance = HttpApplicationFactory.GetApplicationInstance(context);
if (applicationInstance == null)
{
throw new HttpException(SR.GetString("Unable_create_app_object"));
}
if (EtwTrace.IsTraceEnabled(5, 1))
{
EtwTrace.Trace(EtwTraceType.ETW_TYPE_START_HANDLER, context.WorkerRequest, applicationInstance.GetType().FullName, "Start");
}
if (applicationInstance is IHttpAsyncHandler)
{
IHttpAsyncHandler handler2 = (IHttpAsyncHandler) applicationInstance;
context.AsyncAppHandler = handler2;
handler2.BeginProcessRequest(context, this._handlerCompletionCallback, context);
}
else
{
applicationInstance.ProcessRequest(context);
this.FinishRequest(context.WorkerRequest, context, null);
}
}
catch (Exception exception)
{
context.Response.InitResponseWriter();
this.FinishRequest(wr, context, exception);
}
}
NET技術(shù)：ASP.NET Process Model之二：ASP.NET Http Runtime Pipeline[下篇]，轉(zhuǎn)載需保留來源！
鄭重聲明：本文版權(quán)歸原作者所有，轉(zhuǎn)載文章僅為傳播更多信息之目的，如作者信息標記有誤，請第一時間聯(lián)系我們修改或刪除，多謝。
