I
prefer to split them up because I use them in entirely different contexts
within an app, the CRUD DAO is used for editing and the Gateway is
used generally for display - and i prefer smaller, more
specialized cfc's.
---------------------------------------------------------------Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Jason Daiger
Sent: Tuesday, December 27, 2005 8:18 PM
To: [email protected]
Subject: [CFCDev] Table Data Gateway versus Data Access ObjectAfter a ton of reading and experimenting w/ these 2 patterns. Is there a reason folks seem to prefer the TDG pattern as M. Fowler describes, http://martinfowler.com/eaaCatalog/tableDataGateway.html, over the DAO pattern described in the J2EE Design Patterns, http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html? It seems to me the DAO pattern outlined by Sun includes the TDG pattern in that it allows multiple rows to be returned. To me this type of DAO seems 'more complete' b/c it creates a single location for all CRUD functions for a table, or set of depending on the relationships, in one place and not one for the single Curds and one for the multiple CRUDs.Am I missing something or not understanding the TDG correctly?-Jason----------------------------------------------------------
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).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
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).
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
