Well if your calling page is going to be connecting to your facade with
a simple facade.someMethod(argumentcollection=myArgs) then on CF8 you
could probably get away with just using onMissingMethod() in the facade
CFC to determine which object to fetch and run the method against. That
would keep the facade component small and relatively manageable from the
perspective of having lines of code to maintain.
You may or may not want to actually create the work object on each
request - it might be better for reasons of performance and
encapsulation to load your facade with an IoC factory in the application
scope like LightWire or ColdSpring and then use that to fetch whichever
object will do the actual work. That way the IoC factory can be in
charge of managing the dependencies between those objects and
determining if any of them need to be cached because they're used
frequently. You're likey to be reading user objects pretty frequently
for example, so it may make sense to cache them for performance.
Good luck! :)
ike
--
s. isaac dealey ^ new epoch
isn't it time for a change?
ph: 781.769.0723
http://onTap.riaforge.org/blog
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
http://ad.doubleclick.net/clk;207172674;29440083;f
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:316029
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
