ASP.NET, Application Domains and ISessionFactory

Patricius · **Joined:** Sat Dec 09, 2006 10:01 am **Posts:** 1

Hi!

I may have misunderstood some of the guidelines on ASP.NET and session handling that is presented on the NHibernate website. Nevertheless, I dare to ask my question.

The HTTP-modules I have seen implemented, that does session handling in ASP.NET, I think they store session factories in the HttpContext.Application collection. I am just wondering, is anything wrong with storing a single session factory per application domain, i.e. in a static variable/property? I know this is not a viable approach for session objects, but does it also apply to session factories?

Thanks in advance.

mnichols · **Joined:** Mon Aug 21, 2006 9:18 am **Posts:** 179

The session factory is an expensive process to create so typically there would only be one session factory per app domain. In the HttpModules you have seen you should see a check first for whether the factory has been initialized (from the configuration) and if so to NOT do so again.
So calls like this

Code:

Configuration cfg = GetConfiguration();
sessionFactory = cfg.BuildSessionFactory();

should only be done upon the Application startup.

Hope this helps
MIKE