So, are you saying then that turning off cacheRealPath fixed all name conflict issues? The first post you link to is one I wrote asking more about how the underlying mechanism of path resolution works (a related issue to be sure, but not a name conflict issue), and the other is Raymond saying he had not heard of name conflicts. I am tempted to say that absent cacheRealPaths (which not self-respecting shared host should have turned on) there is no name conflict issue with CFCs. That said, using CFCs in a shared server set-up still poses unique challenges -- but in response to Nando's latest inquiry I believe the fears about name conflicts are unfounded.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Massimo, Tiziana e Federica > Sent: Wednesday, November 19, 2003 2:58 PM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] cfc paths > > > > I haven't looked back over the entire thread on this, but did > anyone look > at > > the possibility that this is simply the cacheRealPath issue that has > plagued > > multi-homed CF installations in the past? > > Yes, it's the same issue, just a different incarnation. > > We already mentioned it two months ago: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg01629.html > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg01632.html > > Massimo > > > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word '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]
