> I wouldn't trust that due to CFs caching. > > CF WILL do this (look through the web root) but once it finds a CFC it > caches that location and doesn't look any longer... so the likelihood in a > shared environment is that you'll end up using somebody else's > "security.CFC" unless you adopt a wacky naming standard (and then you're > just hoping somebody doesn't use your components on the same server if you > distribute them) > I use the "wacky names" strategy most of the times, but it doesn't works well whenever you want to distribute apps or CFCs to others (both free or commercial).
We keep saying this over and over, we are facing the same names clashing issues introduced by custom tags with the <cf_tagname> syntax :-( ---------------------------- Massimo Foti http://www.massimocorner.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]
