>>NET handles requests simultaneously - you can't rely on any request completing before another BeginRequest occurs. So, for example, by the time your EndRequest fires there's no guarantee that LXFramework.oResponse is pointing to the object reference assigned in the BeginRequest(). Same type of problem could occur anytime you reference these objects during page processing...
>
>What would you recommend as adjustment in the global.asax to make sure of that? I cannot imagine there wouldn't be a way to process simultaneous hits in .NET without mixing up transactions. I always thought that design in the global.asax was independent per hit.

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?

Regards,
Viv