On that note, was the CFC was including display templates that you could
modify to suit your needs? Or the HTML was actually embedded in the CFC
methods? Why was the CFC used, rather than a procedural front-end using the
CFC as a backend? Just for ease of distribution (one file over many)?
Didn't that make for ugly as hell URLs, particularly the initial request?
Consider the Mach II framework: it uses a CFC for processing all requests (actually several related CFCs). The CFCs are driven by an XML config file that specifies which view files to render. The CFCs include the view files and cascade the views (to allow layout wrapping) and then emit the finished HTML.
The URLs are of the form /index.cfm?event=updatePersonalDetails (the index.cfm file simply delegates to the CFC instance: framework.handleRequest() sort of thing).
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
