Jaime, I think its the correct term. What I had in mind is something like the CartManager in the FuseBox Bookstore Sample application. Here is a brief description
"The shopping cart functionality is handled by a CartManager CFC which acts as a Session Facade. This means the CartManager creates and manipulates a Cart object that is kept in the session scope. The Cart object itself has no idea that it is being held in the session scope. All manipulation of the session scope is handled by the CartManager facade." http://www.briankotek.com/index.cfm?fuseaction=content.viewcontentitem&contentid=47&returnto=coldfusion.main I thought a facade could simplify things. My thinking was - if ninety percent of the dao/gateway components are dependent on siteUser information, maybe would it be easier to pass a facade object into the component contructors instead of requiring a siteUserID on every method. Then again maybe its the "hammer looking for a nail" syndrome :) Janet -- --------------------------------- We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
