On Tue, 20 Jul 2004 23:12:06 -0400, Dave Carabetta <[EMAIL PROTECTED]> wrote: > Yes Sean, this summary is correct.
Good, that means I'm not losing it... :) > 1) If I have cfsetting enablecfoutputonly="yes" at the top of my > calling code, I need to put cfoutput around my cfsavecontent syntax > within my CFC methods. Otherwise nothing is saved in the cfsavecontent > variable. Well, all my methods are output="false" and if I need to use cfsavecontent I'd expect to use cfoutput (that's how quite a bit of my recent code works that generates XML). I don't think this is at all surprising when you think about it... > 2) If I'm uploading a file, the CFC apparently has access to the form > scope in some way. If I pass in a literal string called > "form.uploadFile" then the CFC can somehow "reach in" to the form > scope of the calling page and get the file. Not really, it's more the way cffile works - it needs the name of the form scope variable, not the value... odd, but true. And that's nothing to do with CFCs really. > Does that question make sense? Any insight is appreciated. I'm not sure either of these are really issues if you follow best practices... -- 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 words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
