Greetings, Having read this article by Adam Haskell ( http://cfrant.blogspot.com/2008/10/why-bother-getters-setters.html) and the topic being kicked off by our own Seth Bienek I was wondering what people's thoughts were on this.
I've seen many apps that have been coded with the bean/DAO/Gateway/Service object style of doing things. The beans are nothing but a large collection of getters / setters in most cases. The DAO populates the beans which then get passed around to displays or other functions. Is this just adding lots of overhead to the app? I know this style of coding is not the only way to architect a system, but it certainly seems to be popular and widely pushed among the CF blogs and magazines. But is it a 'best practice' or just lots of extra work for little return? I know, each app should be approached and designed according to its own needs. Does having a set way of doing things (like making beans, DAOs, Gateways, and Service layers) make it easier or harder overall to get an app up and running quickly and keep it maintained over time? -- James Husum The Quixote Project - one guy's quest to make the world a better place - http://www.thequixoteproject.org/ Brainsludge - all the shtuff running around my brain - http://www.brainsludge.com/ Know any writers? I need their input! - http://www.smotu.org/ Currently reading: The Sapphire Rose by David Eddings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [EMAIL PROTECTED] For more options, visit http://groups.google.com/group/houcfug?hl=en -~----------~----~----~----~------~----~------~--~---
