One thing to consider is whether you want to expose NHibernate-isms all over the rest of your application.
/Oskar 2010/2/9 Dietrich <[email protected]>: > I've got a Winforms application with three assemblies, UI, Business > Logic, and Data Access. > > My DAL contains all the queries that the UI uses to do all it's stuff, > and everything is written in the Criterion API, so I think that I've > avoided the parameter bug issue. > > Is there any reason that I shouldn't just make every query in the DAL > return Future<T> or FutureValue<T> rather than List<T> or > UniqueResult<T>? Is there some overhead to worry about with the Future > feature? > > I'm going to go ahead and test this, but I'm worried that it might > look fine in testing and then explode all over the place when I roll > it out to my 100+ users. > > -- > 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. > > -- 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.
