>I see only two choices. Either change the design of your framework to support being shared by multiple sessions or instanciate your framework once for each session. To load the framework once the first time a new client hits the site you would need to scope your framework to session instead of application. Subsequent hits by the client would then be fast since the framework is already loaded to his session. The downside is now you have a copy of your framework instanciated for each session which may cause resource issues on high volume sites.
>

>i.e.:
><object id="LXFramework" runat="server" class="Framework.Framework.App" scope="Session" />
>

>Then change all of your global.ascx subs starting with Application_ to Session_
>
>I do not like using complex frameworks especially for web based applications. The design needs to be kept simple and lightweight. When the asp.net 2.0 release came out the majority of my framework was redesigned around lightweight static classes.

I tried the Session scope last night and dropped it extremely fast. This would not be applicable in our case.

As for the framework, it has been designed to deliver RAD development and contains a DLL of about 400k. The loading sequence does a lot of things which we need them to be stored in memory.

I will have to look into another design to make sure a hit does not collapse into another.