10

I have a long running ASP response (actually an MVC action) that I want to cancel if the user has navigated away. I think this should be fairly simple:

if(!this.Response.IsClientConnected)
{
    Response.End();
}

However I've come across various sources starting that this method is slow.

So I ran my own tests (using MVC mini profiler, though you could use your own):

using (var step = MiniProfiler.Current.Step("Response_IsClientConnected"))
if(!this.Response.IsClientConnected)
{
    Response.End();
}

That found that every time I call it it's consistently very fast: under 1ms on my developer set up. This is whether it's true or false.

Under what circumstances is Response.IsClientConnected expected to be slow?

I have to support IIS6 - would Response.IsClientConnected be slower on that?

Does anyone know what it's doing under the covers? At a low level I'd expect the TCP/IP stack to know whether the connection is still there, so I'd expect this check to be instant, but does IIS have to do some additional work to check?

Keith
  • 150,284
  • 78
  • 298
  • 434

1 Answers1

11

Good question but unfortunately don't have the answer, but can provide the following information. Hopefully this can be a starting point to know what's it's doing under the covers.

The Response.IsClientConnected is checking this by asking the current worker HttpWorkerRequest handling the request.

The worker request can be one of the following types and is created by the ISAPIWorkerRequest.CreateWorkerRequest(IntPtr ecb, bool useOOP) which is called by the ISAPIRuntime.ProcessRequest(IntPtr ecb, int iWRType). This is the entry point from the low level ISAPI to the ASP.NET runtime.

  1. ISAPIWorkerRequestInProcForIIS6
  2. ISAPIWorkerRequestInProcForIIS7 >= IIS7
  3. ISAPIWorkerRequestInProc < IIS6
  4. ISAPIWorkerRequestOutOfProc For out of proc requests

For all the InProc HttpWorkerRequest workers this call is then directed back to unmanaged code by calling int EcbIsClientConnected(IntPtr pECB) which is located in the webengine.dll pECB being the Extension Control Block (ECB), provides all the low level access to the ISAPI request. This reference is initially passed to the ISAPIRuntime.ProcessRequest.

Now I can't find any implementation details of the EcbIsClientConnected method. So without this it's impossible to know what it's doing under the covers and how this maybe differs for the different versions of IIS. Maybe someone else can explain this? I would like to know as well.

Martijn B
  • 4,065
  • 2
  • 29
  • 41
  • Cool, that's a good start, but not the answer. I'll vote it up once I have one. – Keith Feb 01 '12 at 15:54
  • I just asked for the implementation details of the EcbIsClientConnected method on the IIS.NET forums. Hope somebody there knows - http://forums.iis.net/t/1187030.aspx – Martijn B Feb 10 '12 at 11:03
  • Cheers, though it looks like the response is "don't mess with that!" Helpful :-| – Keith Feb 12 '12 at 18:08
  • @Keith One tiny addition I have, is from a Microsoft person I spoke on a conference. He was just thinking out loud but he could imagine that the method could be slow in cases where your client for example is a mobile device on a slow connection. – Martijn B Jun 06 '12 at 13:18