seperating read and write functionality in my repository
Posted on 2012-03-21
I'm just getting to grips with using a repository and interfaces in c# and now have a new thought.
I'm about to start a reasonably sized website that has 3 sections. The public facing, the admin section and the client log in area.
Although it is probably over kill as I am likely to be the only one working on the site I'd like a go at doing this anyway.
What I want to do is split my functionality up so that the public facing website only has access to my read functionality, the client login only code relevant to its purpose and likewise with the admin section.
Am I right in thinking that the best way to do this is to have a generic read interface that a generic repository implements. The same then for the the public facing code and the private log in area?
Does that make sense?
Looking for some constructive input and direction....
Thanks in advance.