> First, 99.99% != 100%. I'm generally fond of fudging in this Errr, I never said it was 100%, and I never said you said it was 100% either. Sorry if I misspoke.
> On that note, was the CFC was including display templates > that you could modify to suit your needs? Or the HTML was Nope. In this case, you either use the default display, or build your own client, ie, you do everything, of course, the CFC still does most of the heavy lifting. What I mean is, the default template cannot be modified on the fly. If you want your own look and feel, you build a custom client. > actually embedded in the CFC methods? Why was the CFC used, The html is done in an include, just to make things a bit cleaner. > 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? Ugly urls? I just post to #cgi.script_name#?#cgi.query_string#. :) ======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ---------------------------------------------------------- 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).
