>When I first encountered this issue back in a beta release, I thought >it was a bug, as well (in fact, I nearly filed it as one), however >someone explained it to me, and it made sense. When I saw this thread, >I couldn't remember what that reason was, so I asked Sean, and he >reminded me that the purpose is to make your ColdFusion code >case-insensitive, even on a UNIX platform. In other words, by >lowercasing the filenames before looking up the CFC, you call call a >component "Person.cfc" or "PERSON.CFC" or "perSON.cFc" in your code, >and "person.cfc" will always be the name looked up. > >It seems strange at first, but it makes sense. It is essentially an >attempt to make CF case-insensitive on a case sensitive OS.
And yet file names for all .cfm files still have to adhere to the usual *nix casing rules. Why not implement this "case-conversion" mechanism for <cfinclude>s and Application.cfm, etc., as well then? Personally, it's not big deal for me, as I'm pretty anal about casing and stuff as a result of being in a *nix environment. But it seems that your logic holds for only *part* of the CF implementation as opposed to across-the-board. If I have to be particular about how I code my template name in a <cfinclude> tag, I should be just as particular about how I code my CFC in my <cfinvoke> tag or my CreateObject() function. Or vice versa. You disagree? Regards, Dave. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
