Hey,

Is there any best practise when it comes to doing alot of NHibernate based activities with ASP?

Currently as im prototyping i have a static class that just creates an NHibernate session the first time its called on a page then re-uses it until the page is destroyed, although this sounds extremely inefficient going forward. Although i cant think of a better way round it unless i can bung it in some sort of ASP wide data area and put some locks around it to keep it thread safe...

Any advice on this area would be great... its not going to be a massive system im working on but it would probably have lots of page hits quite frequently...