> 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. > In that case wouldn't you want DAOManager to remain an interface and then create an abstract implementation? You could then extend the abstract implementation for each scope as needed. Of course CF doesn't have abstract classes either, err, I mean components. -Matt ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
