I'm in the middle of writing a personal project and I'd like to stretch myself a little. This app will be fully AJAX driven, with nearly all of it's programming made through remote calls. I'd like to approach the app via a façade pattern, where a single CFC is my main point of entry, and that CFC simply calls other CFCs behind the scenes. This whole time I've been thinking that would be a perfect scenario for what I thought cfinterface would do for me. But after reading articles from both Bruce Phillips (http://snurl.com/6wngh) and Dan Vega (http://snurl.com/6wnh4) I'm starting to think that my understanding of cfinterface was flawed. So I'm coming to the list for help
Up until a few days ago I was under the impression that an interface was my single point of entry to back end. That I might be able to "include" methods from any number of CFCs in one "interface" to my application. It appears though that cfinterface is mostly used for type checking? Anyway, this is what I'm trying to accomplish: http://www.commadelimited.com/uploads/facade-pattern.gif The façade would have ALL methods, from all CFCs contained within it, but each method would simply be a pointer to the appropriate CFC via a CreateObject statement inside that method. I like this idea because then there's only one CFC which needs remotely exposed methods, and my front end code only needs to worry about one point of entry. I'd like to get some feedback (and debate) on the potential positives and negatives of this approach. Anyone? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:316027 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
