There was mention of NHibernate.Web, but to be clear, the latest patch
in NH-2263 doesn't require that sort of split. It uses reflection/
delegates to access HttpContext.Current.Items. Note that this
property is the only thing in the whole NHibernate framework that
depends on System.Web and prevents that part from being client profile
compatible. In any case, I believe the provided patch solves that
particular issue in a reasonable manner.
The logging story is obviously a bit more complicated. It seems for
the long term, there are a number of goals. Here's a distilled
version of what I'm hearing.
1. Ability to choose logging framework is desirable. This provides
benefits such as unified logging with other libraries and
applications.
2. Ability to hook into log messages via code or configuration.
Without this, life is far more difficult for systems such as NHProf.
3. Ability to support client profile.
4. Simplification of library usage through reduction of dependencies.
Are there any goals missing here?
Patrick Earl
