>I suppose you could use a token so that .BeginRequest() waited until .EndRequest() had fired - but you would be forcing the application to process requests sequentially and probably suffer a nasty performance hit. I guess the question really is why do you need to hold references to the Request/Response objects at application level?

Throughout the framework, I make extensive use of the Request and Response objects. So, I hook them up as framework properties so I can have a reference to them. Do you have a suggestion of another way of achieving this?