Does anyone know if Macromedia has officially acknowledged the issue relating to CFCs and debugging output? In my tests, complex CFCs (such as Mach-II apps) execute upwards of TEN TIMES faster with debugging turned off in the CF Administrator. Anyone know why this is, and if MM has flagged this as a bug or made recommendations about it?
Was this ever declared a bug? I just thought it was a by-product of how the debugging implementation works. I think it had something to do with run-time registering of all the component/method calls with the debugging service. I'd love to see it sped up, but I don't think it's the end of the world either, considering this is a development-only feature.
The real issue I'd like to see looked at is following nested includes in the debug template output for execution times.
Regards. Dave.
_________________________________________________________________
Dream of owning a home? Find out how in the First-time Home Buying Guide. http://special.msn.com/home/firsthome.armx
----------------------------------------------------------
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]
