Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m developing an API for use by one of our vendors to access data in our databases and I need to name my classes. I’m thinking about names such as Retriever, Accessor, and Controller (eg. TimesRetriever, TimesAccessor, TimesController, etc). These classes will provide read only access to data (that I’ll be summarizing) in our database. Is there a commonly agreed upon naming convention for what I’ve described?
Martin Fowler (www.martinfowler.com) is a good source for these types of question; since, you’re really talking about design patterns.
My best guess would be the Repository pattern (http://martinfowler.com/eaaCatalog/repository.html).
From the site:
Sounds like what you are trying to do.