Hibernate version: 1.2 Alpha

Hi
In the main page of nhibernate exactly in the key features section,there were written:


But i did not read any post in the forums that supports the long-lived sessions , so i thought that there may be a catch that i don't know.
So please tell me the main troubles that would happen if i let one session open for the entire application running time (Performance impacts,memory impacts,exceptions,etc..).

PS:I am using Windows Forms 2.0 not Asp nor Web Services

I know that were mentioned before 1000 times but i am totally messed-up.

First you have to do a clear distinction between a SessionFactory and a Session.
You would like to keep your SessionFactory for the lifetime of the application.
It is thread safe and an expensive object to build.
On the other hand a session is not thread safe and not exception safe. This means that if your session throws an exception you should close it immediately.
In your winforms app you should have a session per operation or another usage pattern but not a session for the lifetime of the application. Also an open session keeps an open connection to the database and you would not want to do that.
The meaning of the "conversation" paragraph in the docs is that you can load an object in one session, close the session but keep that object in the memory. In another operation (and a fresh session)you can save the object in the db. This means that the lifetime of your persisted object is longer than the lifetime of any individual session.

HTH,
radu