> DAO - existing component > DAOManager - role-based way of managing DAO (a facade of sorts) > DAOManagerSession - extends DAOManager, interacts with session scope > Client - uses what it thinks is a DAOManager (but the actual > instance > is determined by whoever creates the specific instance) > > Make sense? > Smells of interfaces to me. Wouldn't DAOManager be an interface and then have an implementation that is done using the session scope? Then the client would make use of the interface methods without knowing the underlying implementation.
But wait! There are no interfaces in ColdFusion. Doh! -Matt ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
