Jeff, the problem is that Macromedia does NOT have a clear declaration
that debugging should be turned off on a production server.  The 6.1
docs say this:

"You should disable debugging output on production servers. Doing so
increases security by ensuring that users cannot see debugging
information. It also improves server response times. You can also limit
debugging output to specific IP addresses; for more information, see
Debugging IP addresses page."

Note the last sentence, which could easily lead someone to believe that
limiting the output to 127.0.0.1 would have the same effect, which it
does NOT.

The closest thing to a recommendation I can find is here:

http://www.macromedia.com/support/coldfusion/ts/documents/tn17259.htm

And it clearly says:

"Macromedia recommends that for all ColdFusion production servers, at
least one specific IP address be specified in the Debugging section of
the ColdFusion Administrator."

In my opinion, MM should first acknowledge this as a bug, and second
release a crystal-clear recommendation to TURN OFF debugging and not
just limit the output to one or more IP addresses.


> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeffry Houser
> Sent: Monday, March 01, 2004 2:49 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [CFCDev] CFCs and Debugging
> 
> 
> 
>   I will point out that the original poster said  "complex 
> CFCs (such as 
> Mach-II apps) execute upwards of TEN TIMES faster with 
> debugging turned off"
>   The last three words are key "debugging turned off."
>    I'm sure all of us know that debugging should be turned off on a 
> production server.  I have not done any tests as to how 
> debugging affects 
> performance, though.
> 

----------------------------------------------------------
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]

Reply via email to