Amen to that. DAOs are only a small piece of an OO application, and the problems they solve can easily be solved other ways, though in my opinion, not as elegantly. And DAOs are irrefutably incapable of handling the entire persistance layer for an application (JOINs are a big reason), so you still need other pieces in your persistance layer (I like gateways).
Consistency is about consistent application of methodologies, structures, and patterns, not about applying a specific set of those. However, if you use a specific set that other people use as well, that can bring some advantages into play. For example, ever seen a CF developer position advertised that specifically requests Fusebox/FLiP experience? cheers, barneyb On 19 Aug 2005 00:19:20 -0000, [EMAIL PROTECTED] wrote: > I totally agree. Somehow I feel like most of the active voices in this list > have decided that the ONLY way to do OO data is to use the common DAO pattern. > While I prefer a less 'Pure OO' for most of my data work, my code is still > more OO then not. When I need a more pure Object, I make it more pure to fit > my needs. > > The other silly argument I've read in this thread is that you > must be consistent in your programming, implying that you need to do a fully > tricked out OO design in order to be consistant. > > It is possible to be consistant > without following the <insert somone else's favorite pattern here> pattern. > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
