title: mixing NHibernate with 3 tier developing
body: <p>I have a 3 tiered app:
  1st layer: SQL DB.
  2nd layer: App Sever (dotnet)
  3rd layer: smart wpf client.</p>
  
  <p>I'm using NHibarnate (fluent) as the data source for the application server layer
  (App server- 2nd layer talks to  DB using NH)</p>
  
  <p>Application layer talks to the client using WCF.</p>
  
  <p>Do I benefit anything from using NH - as WCF doesn't support NH lazy loading (at least it doesn't look like this) and - if I use a static session object - I have to make the server single instance single concurrency - otherwise things get messy inside NH when more than one call comes at the same time.  If I open a session object (NH) for each call and close it at the end of the call - I loose the NHibarante 1st level cache...</p>
  
  <p>So - The question is - am I implementing NH wrong ? or is it not suppose to be efficient in my kind of project ?</p>