On 6/14/05, Peter H <[EMAIL PROTECTED]> wrote: > I think the premise is that if you cfoutput the whole page, the whole page > has to be parsed where as if you cfoutput selected parts there is less work > for the page processor to do.
Since the whole page is compiled ONCE and then just executed, I'm not sure what you mean. Perhaps it was true in CF5 but that argument doesn't really make sense with CFMX. > I tried this today for a reasonably complex page to see it would make a > difference. Initial findings are that it did but the difference wasn't big. One thing that *might* be different is the generated whitespace. If you have <cfoutput> only around stuff you want in the HTML stream, then CFMX will generate less whitespace and that might lead to some minor performance differences... -- Sean A Corfield -- http://corfield.org/ Team Fusebox -- http://fusebox.org/ Got Gmail? -- I have 50, yes 50, invites to give away! "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' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
