Of course, because we will be CFMX compatible, we have started to use CFCs, and we've met the problem that makes impossible to use CFCs in shared hosting environments. That means that you can't distribute your CFCs in one of your site's folders, as you cant reference them with "../cfc/cfc1".
Could someone tell me how to trigger this problem? I haven't been able to get this problem to crop up, and without being able to understand it I am worried that it will crop up at the most inopportune time.
My current setup:
* CFMX 6.1
* Windows NT
* Apache 2.0.47 with IP-shared virtual hosts for each site
* no mappings at all in the CF Administrator
* Apache "Alias" command setting /CFIDE/ to
C:\apps\CFusionMX\wwwroot\CFIDE\
* webroot of sitename would be D:\web\sitename\
* cfcs for sitename would be in D:\web\sitename\system\foo
* same for custom tagsWe reference all of our cfcs either relatively from the same directory, or from the webroot:
Application.User = createObject("component", "system.User");
We reference our custom tags also from the webroot:
<cfimport prefix="layout" taglib="system/tags/layout" />
This works even when we have cfcs and tags with the same names for different sites, like this:
D:\web\sitefoo\system\User.cfc D:\web\sitebar\system\User.cfc
"sitefoo" won't access the "sitebar" code, nor visa versa. So, what gives? Why do I seem so blessed as to not encounter this problem plaguing everyone else?
--
Ben Curtis
WebSciences International
http://www.websciences.org/
v: 310 478 6648
f: 310 235 2067----------------------------------------------------------
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]
