> It's generally considered a 'bad thing' to use CFC's to output html, > as they are better placed in the logic tier of an application, rather > than in the output.
I'm going to ride the other gravy train on this one. You certainly shouldn't put <CFOUTPUT> statements in your CFC's (and just generate the HTML to be output by the calling page). But it is VERY valid to encapsulate output generation in a CFC (not necessarily the same CFC's as the business logic though). Why would you do this? Because then you can just instantiate a different "UI" CFC (that supports the same method set/interface) and you don't have to change any of the code that uses that object. The actual CFM page then become the "glue" between your business logic and your UI. You could even create a "glue" object for a page that provided a facade onto your business and UI objects. Just an alternate point of view. Regards, Gary Menzel --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
