> As it stands, it seems that using CFCs on a shared host is still a major > challenge. I find I need to either use relative path "slash notation", > which requires that the CFCs live in a directory under the calling page or > in the same directory as the calling page (because you can use a path like > "../org/bacfug/test" but can use a path like "org/bacfug/test") or use the > TemplateProxyFactory trick to instantiate a CFC based on a fully qualified > file path (which I've resorted to recently). Have others faced these > challenges on shared hosts and have answers I'm not seeing?
Yes, calling CFC on a shared box can be quite challenging. In my opinion we need something that would emulate <cfmodule> for CFC or, at least, have something like "../org/bacfug/test" work. What I am doing is to store the CFCs inside a custom tag directory defined from the CF Admin (most hosting companies will create it for you). From there, I can call the CFCs using dot notation as if the custom tag directory is the root of the website. Another scary thing is that CFCs, like custom tag not called using <cfmodule>, may be cached by CF Server... This may lead to clashes among different files ---------------------------- Massimo Foti Certified Dreamweaver MX Developer Certified Advanced ColdFusion MX Developer http://www.massimocorner.com/ ---------------------------- ---------------------------------------------------------- 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]
