Handling Exceptions in an IHttpAsyncHandl er Page

[Brad Quinn]

I have a question about the correct way to handle exceptions. Most of the
sample code I have seen doesn't address this.

My BeginProcessReq uest looks like any other.

public IAsyncResult BeginProcessReq uest(HttpContex t ctx,AsyncCallba ck
cb,object obj)
{
AsyncRequestSta te reqState = new AsyncRequestSta te(ctx, cb, obj);
_threadPool.Pos tRequest(new WorkRequestDele gate(this.Async ProcessRequest) ,
reqState);
return reqState;
}

The first difference is in AsyncProcessReq uest, where I put a try/catch
block around the call to ProcessRequest.

void AsyncProcessReq uest(object state, DateTime requestTime)
{
AsyncRequestSta te reqState = state as AsyncRequestSta te;
try {
base.ProcessReq uest(reqState._ ctx);
} catch(Exception e) {
reqState.Except ion = e;
}
reqState.Comple teRequest();
}

I have also added an Exception property to my AsyncRequestSta te.

And finally I re-throw the exception in EndProcessReque st.

public void EndProcessReque st( IAsyncResult ar )
{
if ( ar != null ) {
AsyncRequestSta te reqState = ar as AsyncRequestSta te;
if ( reqState != null && reqState.Except ion != null ) {
throw reqState.Except ion;
}
}
}

Is there anything wrong with this strategy? I use remoting heavily and
occasionnaly get bad behavior when running asynchronously.

Thanks,
Brad