Re: [CFCDev] DAO vs. Gateway?

[Jason Daiger]

My .02 on the DAO's getting huge is the same response given when Model Glue folks that complain the configuration file that is too long. Use a good editor and you probably won't even notice the size.  For me managing 2 small files is a bigger pain than 1 large file.  Also, I'm not making any comments on the editor folks are using (obviously since I have no idea what people are using) but I've found the code collapse w/in Eclipse eliminates the big file concern for me. Thus I'm left with the 'keep track of 1 or 2 files' issue and I simply choose 1 approach.  I have yet to hear of a design reason why the 2 file approach is better or why a 1 file approach would break the design pattern both approaches strive to achieve.  In the end, it seems like personal preference.  Now if someone tells me the 1file approach breaks down because of X or breaks a design pattern b/c of Y then I'm all ears.  Until then, it's 1 file for me. Peter J. Farrell wrote: Kurt Wiersma said the following on 3/1/2006 12:52 PM: Like Chris Scott, I have found that the Java convention seems to be having all the code in a DAO class. In my CF apps I have found I really like having the gateway separate because in Java I have found my DAOs get huge with all the different methods that sometimes have to be added for reporting purposes. --Kurt Ditto! Although I don't do any Java developing, I have found that DAO classes with everything gets unwieldy after a bit of time. Also, I like the idea of having my DAO access single records, while the Gateway is one or more. Secondly, typically my DAOs return populated beans while the Gateways returns cf query objects. .Peter -- Jason Daiger URL: www.jdaiger.com EML: [EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org 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). An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org