>> I am not likely to agree that calling a cgi variable inside a CFC is a violation of good code.
>Which is exactly why trying to argue with you is somewhat pointless [etc] Firstly: I tend to side with Sean, in *theory*. However... Given CF is a web-development platform, and given CGI variables intrinsically exist during a given request (are there situations they don't? Webservices or something?), is it breaking encapsulation any more than - say - using isDefined() (it's not like it's a method of your CFC!), to *assume* CGI.SCRIPT_NAME is available to use? Yesyes, "don't use out-of-scope variables", but is saying "don't use CGI variables" not kind of like saying "don't use some inbuilt function that returns the value of pi"? Sometimes dogma should give over to good sense. One might argue that "you might port your code to something that doesn't furnish that CGI variable you're relying on". Well... *sure*, that might happen. But you're going to have more issues than just a couple of suddenly-non-existent CGI vars. Adam ---------------------------------------------------------- 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]
