I am using the latest copy of NHibernate and have decide to implement the MVP on the GUI side of things to help separate actions from each other and improve the unit tests that I can write.

I have a presenter and view that are implemented in various user controls so that I can drop these simple actions onto a page to get the results that I need. When I only put one user control on a page then everything works great. I have successfully put two user controls on a page and they both load the data as required. However the problem comes when I try and save any changes that are made on the screen. Both are tied to the same link so that you click the save button and the application will be saved. Since I want both user controls to function independent of each other. All the page does is tell each user control which application they need to display and what to do if a page event happens, an error happens or success happens (in this case the page redirects to the next page).

The page has a button to save, the event of clicking the save button fires the save application function of both user controls. In order to handle events correctly without problems when each event is fired it is spawned off into its own thread. Here is my problem I can't get both user controls to save. If I remove one of the user controls completely then everything works perfect but once I add the second control and the second thread then NHibernate no long registers that the second user control did anything. So it doesn't recognize a change.

My understanding is that the page requests a session from NHibernate and then passes it to each of the user controls. And because each user control is running independent NHibernate is passing the same session to both user controls. Which I think is were my problem is happening. I am trying to solve the problem without managing the sessions on such a granular level as it increases coupling which I am trying to avoid.

Does anyone know where I can go to look for help or has help for me directly?

The last time I used NHibernate with ASP.NET we followed the session per request pattern - basically each web request is a unit of work (session). To manage the session we created an HttpModule. We were also using multiple user controls which implemented the MVP pattern for testability etc. just as you are. There are many good articles about this, here are a couple:

http://www.codeproject.com/aspnet/NHibernateBestPractices.asp
http://blogs.intesoft.net/simon/articles/16.aspx