>You don't want to go thorugh all of this. A static property hung off an object somewhere will let you keep a single instance of your oApp object around. You don't want to require a special page class just to recreate this object - you should should treat the oApp object as a singleton which is going to be much more efficient resulting in smaller memory footprint (no objects created over and over for every hit).
>
>Performance is probably not a big concern if hte instantiation is pretty light weight, but if you're doing things like reading settings from an INI (as you mentioned earlier) file you surely don't want to do that on every hit!
>
>Actually looking at this a little closer - a static won't work if you're assigning request specific items to this object. Why are you even storing Request and Response? Those objects are ALWAYS available with:
>
>HttpContext.Current.Response
>HttpContext.Current.Request
>
>from anywhere where HttpRequest/httpResponse are visible.
>
>There's no need (in fact it a bad idea because the object reference may keep the garbage collector from cleaning up the references if your code fails to clean up its object) to save those vars.

I will reply to the other message you just sent with all the related information.

Thanks