Are child requests supported in Integrated Pipeline Mode?

brettle — Wed, 11 Jul 2007 18:28:38 GMT

Hi,

The HttpWorkerRequest documentation states:

... your code could create a derived class for the purpose of child-request execution within a given application in order to pass its instance to ProcessRequest. In this case, the derived class should keep a reference to the current HttpWorkerRequest and delegate most of the methods to it.

My NeatUpload component does exactly this and works fine in Classic Pipeline Mode under IIS7. However, in Integrated Pipeline Mode the child request seems to silently fail. I'm logging calls to all of the overrideable .NET 1.1 methods of HttpWorkerRequest and I see the following sequence of calls:

GetFilePath()
SetEndOfSendNotification()
GetHttpVerbName()
GetQueryStringRawBytes()
GetQueryString()
GetServerName()
GetProtocol()
GetLocalPort()
GetUriPath()
GetRemoteAddress()
EndOfRequest()

Note that SendStatus() is never called and neither SendResponseFromFile() nor SendResponseFromMemory() is called. That combined with what I read in an earlier thread on this forum make me think that child requests are not supported in Integrated Pipeline Mode. Is that true?

NeatUpload uses child requests in 2 different ways. First, to extract uploaded files from the entity body a BeginRequest handler 1) creates a child request that delegates most methods to the original request but overrides methods like ReadEntityBody() to do the file extraction, and 2) passes the child request to HttpRuntime.ProcessRequest() and calls CompleteRequest() on the original request. Second, to make the progress bar work in a web garden/farm environment, the upload status is stored in the session and needs to be updated periodically during the upload. Since we don't want to lock the session for the entire upload request, child requests are used to update the status in the session.

If child requests are not supported in Integrated Pipeline Mode, does anyone have any recommendations on alternative ways to manipulate the entity body or update the session without locking it for the entire request? The only possibility I've found for manipulating the entity body is using IHttpRequest::ReadEntityBody and IHttpRequest:SetEntityBody from a native module. The only possibility I've found for updating the session without holding a lock on it involves using methods of ASP.NET 2.0's SessionStateProviderBase. I haven't tried either, so if there are better alternatives or I'm on the wrong track, please let me know.

Thanks,

Dean

Search results matching tag 'HttpWorkerRequest'

Are child requests supported in Integrated Pipeline Mode?