I thought the default http handling was synchronous, but that's not the behavior I'm seeing.
<div>
When I debug into the MVC 2 source, ProcessRequest never gets called on MvcHandler, only BeginProcessRequest. I thought explicit actions had to be taken in order to use asynchronous handling (like deriving from AsyncController, etc), but this seems to happen
on every request. Was I just mistaken about synchronous being the default, or did some strange setting get set without me realizing it?
Any help will be greatly appreciated because this is driving me a little crazy.
With the addition of AsyncController, the MvcHandler class needs to be an IHttpAsyncHandler now, which means that as far as the ASP.NET core runtime is concerned, the entry points are now BeginProcessRequest and EndProcessRequest, not ProcessRequest.
Kepler
Member
76 Points
42 Posts
Is IHttpAsyncHandler the default in MVC 2?
Apr 16, 2010 03:35 AM|LINK
I thought the default http handling was synchronous, but that's not the behavior I'm seeing.
<div>When I debug into the MVC 2 source, ProcessRequest never gets called on MvcHandler, only BeginProcessRequest. I thought explicit actions had to be taken in order to use asynchronous handling (like deriving from AsyncController, etc), but this seems to happen on every request. Was I just mistaken about synchronous being the default, or did some strange setting get set without me realizing it?
Any help will be greatly appreciated because this is driving me a little crazy.
</div>IHttpHandler IHttpAsyncHandler BeginProcessRequest
bradwils
Contributor
5757 Points
690 Posts
AspNetTeam
Microsoft
Re: Is IHttpAsyncHandler the default in MVC 2?
Apr 16, 2010 04:25 PM|LINK
Short answer: yes.
With the addition of AsyncController, the MvcHandler class needs to be an IHttpAsyncHandler now, which means that as far as the ASP.NET core runtime is concerned, the entry points are now BeginProcessRequest and EndProcessRequest, not ProcessRequest.