using IoC and programming to interfaces, you can decouple your code without the strict 'layer can only access its immediately inferior layer' rule
On Thu, Mar 19, 2009 at 2:03 PM, Humberto Marchezi <[email protected]>wrote: > Hi all, > > We worked with layered architecture: > - UI Layer > - Service Layer > - Domain Layer > - Persistence Layer > > A layer can only access its immediately inferior layer. > Thus service layer can not access persistence layer directly. > > The problem is that our DTOs classes are associated to the service layer. > However due to performance issues, we have being thinking of using DTOs > directly in the persistence layer. > By doing this, we expect Linq-to-NHibernate to directly generate a list of > DTOs in a optimized way. > > Is it a good practice ? > How to you handle this problem ? > > thanks > > > -- > Humberto C Marchezi > --------------------------------------------------------- > Master in Electrical Engineering - Automation > Software Consultant and Developer > at the Town Hall of Vitória > > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
