We host many virtual Web sites for third part developers. We do not offer staging servers unless performing major upgrades (switching to ColdFusion MX, for instance). Unless I'm mistaken, I think this fairly common.
We used to enable debugging on the production server. By default, only the local loop back address was listed. If a developer needed to work through a problem, they could call and request that we add their subnet. That worked pretty well. However, when we made the switch to ColdFusion MX, performance was so terribly slow that, when we discovered it was the debugging option, we were forced to cancel this practice. I would hazard a guess that most ColdFusion applications are hosted on shared servers in an environment that developers cannot reproduce locally. In fact, the production environments are going to be radically different, utilizing things like sandbox security, least necessary file system privileges, URLScan and many other utilities that could easily break an application, throw a cryptic error message, and be terribly difficult to debug. In a perfect world, no one would work of the production server and there would be a staging server which precisely duplicates the production environment. Unfortunately, that's not the case. So, it would be nice if debugging didn't noticeably affect the performance of all requests and performed better when activated. Ben Rogers http://www.c4.net v.508.240.0051 f.508.240.0057 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Liotta Sent: Monday, March 01, 2004 5:06 PM To: [EMAIL PROTECTED] Subject: Re: [CFCDev] CFCs and Debugging Why would you need debugging on a production server at all? If anything you would need to debug should be done on the development server. Or if it is some specific deployment issue then that should be debugged on the staging server. -Matt On Mar 1, 2004, at 4:54 PM, Brian Kotek wrote: > That would be nice. Up do now, most of the info at MM related to > making > sure you specified an IP address so that debugging info didn't get sent > out to unauthorized people. Which was fine, until recently. Now, that > just isn't the right approach: it's clear that debugging, or at the > very > least "report execution times", really *must* be completely turned off > on a production server. Particularly if the server hosts any apps that > use CFCs. Wouldn't you agree? > > Thanks, > > Brian > > >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of Sean A Corfield >> Sent: Monday, March 01, 2004 4:46 PM >> To: [EMAIL PROTECTED] >> Subject: Re: [CFCDev] CFCs and Debugging >> >> >> On Mar 1, 2004, at 1:38 PM, Brian Kotek wrote: >>> This is all coming up because our server admins had no idea >> about this >>> so I am having to give them a crash course and explain why >> I'm asking >>> for this on the production boxes. Sean, any chance MM can >> make a more >>> definitive statement about this for server admins to understand the >>> issue? >> >> What are you looking for? "Debugging should be turned off on >> production >> servers."? >> >> I can ask what the position is internally... >> >> Sean A Corfield -- http://www.corfield.org/blog/ >> >> Got Mach II? -- http://www.mach-ii.com/ >> >> ---------------------------------------------------------- >> 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] >> > > ---------------------------------------------------------- > 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] > ---------------------------------------------------------- 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] ---------------------------------------------------------- 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]
