Back to list
Views:   0
Replies:  0
Archived
,
Reply 1
I would suggest you to read http://www.primaryobjects.com/CMS/Article108.aspx for understanding Respositry pattern.
Raghu Raghavan, Feb 01, 2011
Reply 2
To make   design Loosely Coupled!
Mohammed Sarfaraz, Jan 23, 2011
Reply 3
Rather than The Controller => Repository => Service  the following is more flexible approach

Controller => Service => Repository => Data Access Engine

Because, the service should be the entry point into your app and this will help you in case where request is coming from different clients like web, portable device, smartclient etc....to manage all the logic at one place rather than splitting between repository and services.

A good writeup on repository pattern can be found here  http://blogs.hibernatingrhinos.com/nhibernate/archive/2008/10/08/the-repository-pattern.aspx

Hope this helps.

Rajesh Pillai, Jan 10, 2011
Stay Inspired!
Join other developers and designers who have already signed up for our mailing list.
Terms     Privacy     Licensing       EULA       Sitemap      
© Data & Object Factory, LLC.
Made with    in Austin, Texas