I got this from "NHibernate in Action" book. This is what is says in book
NHibernate’s built-in current session context implementations
Short name Description
*managed_web This context was the only one available in NHibernate 1.2.0. However, it is now
deprecated. You should use web instead.
*call This context uses the CallContext API to store the current session. Note that,
althought it works in any kind of application, it isn’t recommended for ASP.NET
2.0 applications.
*thread_static When using this context, sessions are stored in a static field marked with
[ThreadStaticAttribute]. Therefore, each thread has his own session.
* web This context uses the HttpContext API to store the current session. It is
recommended for Web applications (and only works with them).
[/quote]
Now I've been away from NH for a while, and I wonder if anything has changed. Is this now in 1.2.1 release?