For what purpose?Abstraction for the sake of abstraction? On Sun, Mar 1, 2009 at 2:20 AM, Graham Bunce <[email protected]>wrote:
> > Ayende: I agree about using the common logging mechanism outlined in > the development post but agree with Tuna that if you can change > NHibernate logging to use inbuilt .NET listeners or, failing that, > abstract out and have your own simple interface that third parties can > use to create a bridge into their own logging mechanism. A Log4Net can > be provided as default..... though this is the same principle as the > "common logging" outlined before, its under NHibernate's control. > > However, abstracting out - however its done - must be a good thing > surely, as its the whole principle of "code to an interface" i.e. let > me decide how I want to log. > > I accept its not a big priority but, from reading the development > thread it didn't sound a huge job either. > > Tuna: Yes, I can and its something I'm going to have to look into I > guess. The development thread raised by hopes that I wouldn't have > to :) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
