Hi,

>But, on all other hits, I am creating a private property of that global application object and use that instead. As this is private, this could work. What do you think?

Don't think that would work. You've always got just the one instance of your framework object that's potentially being hit from multiple threads. You could map your framework oRequest/oResponse properties to the current objects e.g:

  Public Property oResponse
        Get
           Return HttpContext.Current.Request
        End Get
   End Property

In the end, when you make a call to your framework object, you cannot assume that any per-request based information in it relates to the request actually making the call. In fact I think you have to address the general concurrency issues - all methods of the framework would need to be threadsafe (maybe Application.Lock()?) - and that's another performance hit (not sure about this - I've a feeling that HttpApplication itself is threadsafe to some degree but I've no documentation to hand).

I hate to say it but, although you could get this to work, I think it would be wise to rethink the design of the application...
Regards,
Viv