hmm. This sounds too complicated for the average user, but I am curious to know more about this.
For the same reason I am hesitant to have multiple files extending a base class. For that I like mark's suggestion about the single cfc. I want this to be as plug and play as possible for people. >What I did in some of my projects was to have a base method "person" that >the other methods used. Enforce type or variable checking in >getPersonByType, but have the bulk of the work done in the getPerson method. > > >andy > >Hi there Jeff > >I think this depends. Who are you writing the API for? I.e is this >something you are going to use then let other people use it via RiaForge? >Or Are you just developing it to be open source from the get go? > >I am inclined to have one big file as then it's simple to use as you >instantiate it and check out the methods. On the other hand, you might >want to return sub objects from your methods (such as arrays of people >etc) > > >With regards to Question 2, I simpler methods that are more descriptive >would help, such as: > >getPerson(id) >getPeople(Since [optional]) >getPeopleByTitle(title) >getPeopleByTag(tag) >getPeopleByCompany(companyid) >getPeopleBySearch(searchterm) >getPeopleByCriteria(criteriaStruct) >createPerson() >savePerson() >deletePerson() > > > >I hope that helps. > >Regards > >Mark Drew > > > > >On 16/04/2011 08:08, "Jeff Gladnick" <jeff.gladn...@gmail.com> wrote: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343800 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
