Another simple
question. I understand that "best practice" for non-trivial applications is
often to have entityService wrapping entityGateway and entityDAO with the
DAO wrapping persistence implementation spercific code (e.g. SQL commands or
write to file for XML) for single entities and the Gateway providing access to
multiple records.
Two
questions:
- Do you usually
include SQL in the gateway or ask the gateway to wrap list based methods in
the DAO to fully encapsulate knowledge about the persistence
layer?
- Secondly, could
you give a sense of a use case where there is value in having a separate Gateway
as opposed to just having a simple entityManager (with getByID, getList, save,
delete and all other required methods) as the service layer speaking directly to
entityDAO which handles all persistent access and can be called using abstract
factory to support n-persistence options? I'm just trying to understand what is
philisophically different between persisting n objects and persisting
one.
Any thoughts
appreciated.
Best Wishes,
Peter
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
