I guess the real question is whether the team wants to explore nhibernate outside of the ORM domain. Does the team want nhibernate to be nhibernate framework or continue to keep it nhibernate orm?
-Carlos Practice makes perfect, but if no one is perfect, why practice? > From: [email protected] > Date: Mon, 18 Oct 2010 12:41:05 -0300 > Subject: Re: [nhibernate-development] Re: Planning NH next > To: [email protected] > > I'm already doing (doing mean exactly doing) some of those works where > I think is the right place. > - audit : talking with Simon and Roger and helping with some code > - validation: working in NHibernate.Validator that has very few few > things in common with Hibernate.validator > - INotifyPropertyChange writing a post to demostrate how do the > integration having a little performance advantage in less then 50 code > lines. I'm ignoring any other possible support. > - security: I have asked explication and I'm still waiting > > About fork NH: I have invited people to do it more than one time, > after NH3.x we will move to Hg or Git and who want can do it even more > easy. > > To resume: > I still waiting the definition of > - NH "look like depends on the direction where the wind comes from" > - "professional toolkit" and why NH can't be defined a "professional > toolkit" already > - "security" what exactly mean for NH > > -- > Fabio Maulo > > > El 18/10/2010, a las 10:59, Frans Bouma <[email protected]> escribió: > > >> On Mon, Oct 18, 2010 at 3:55 AM, Petrov Peter <[email protected]> > >> wrote: > >> I think Frans Bouma has unbelievable patience. We aren't far from > > the > >> time when Frans will say "enough is enough" and I fear it will soon stop > >> following this dev group. It will be a loss for the NHibernate project. > > With > >> his attitude Fabio will force back other people too. For mr. Maulo it's > > time > >> to reconsider his attitude toward others and his sharp tone. > >> > >> Perhaps you can add some opinion about the initial post of the thread > >> instead try to be "the paladin of justice". > >> Frans can say that he want see auditing, validation, > > INotifyPropertyChanged > >> and security inside NH-core and I can write my opinion and ask for > >> clarifications, then the decision is not mine but of the team. > > > > I wrote on Thursday: > > "The examples I mentioned are not things you expect on the core O/R mapper > > level, however they're all services which build on top of the O/R mapper > > core and utilize it, which also means that if you use NHibernate, and you > > want to use the features I mentioned, you need to implement them somehow so > > they utilize NHibernate." > > > > Google groups link: > > http://groups.google.com/group/nhibernate-development/msg/e91d2b8e8bd202bd?h > > l=en > > > > I never said it should be part of the core, as those aren't core NH > > services. You have apparently no clue whatsoever I was talking about, which > > explains your replies. > > > > Anyway, you have a narrow focus on where NH should go to, but you > > don't realize that this focus only targets core O/R mapper functionality, a > > problem solved years ago already, which means that there's little to nothing > > to do in the future except re-inventing wheels, like we see already with yet > > another xml / code based mapping system and yet another query system. > > > > IF I'll eventually say "Enough is enough", I'll fork NH and do what > > I explained here. But that takes time and I've to look into what it brings > > me, compared to the effort to invest. > > > > FB > >
