On Saturday, August 3, 2002, at 04:31 , Matt Liotta wrote: > 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.
Not necessarily. DAOManager would probably have some default implementations of methods. Particularly if you knew if was all about resultset scope management: you could have private setInScope() / getFromScope() methods in DAOManager that simply threw exceptions but have all the wrapper methods present (that delegate to the aggregated DAO - the data member instance) and then use setInScope() / getFromScope() to store / retrieve results. Specific derived managers would implement those two methods for session scope, application scope etc. "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com 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
