> Not to be the odd one out, but I for one, _don't_ think there should be > relative cfc calling built in to createobject() cfinvoke et all. I think it > provides more problems and questions on useage than it solves. Jim's > mentioned a few that would be apart of the "relative situation".
The issues raised by Jim are important, but they scare me much less than the risk for name clashing... I don't pretend to say relative paths are the ultimate solution, but we have a problem, a pretty serious one, and we need a solution. > Personally I wouldn't mind seeing cfimport > expanded to be able to call in a set of 'classes' from a package directory. > It would give you the extendability you're looking for in redistribution and > allows for a more sound approach IMO of course. (removing the base template > calling only restriction will help) Yeah, expanding cfimport to work on CFC as well would be nice, I am not sure it would solve the issues raised by Jim on CFCs as argument values, but it may be better than plain and simple relative paths > In a perfect world you'd have all shared servers allocating different > instances for each site. CFMX's requirements in hardware certainly hampers > this situation. The weight of BlueDragons' instance on another hand.... Sure, but we don't live in a perfect world... > Again, nothing against realative paths in general, if you need them it's > possible with a little coldfusion api comming into play. (except > argument,extend naming) I personally think it's going to cause more pain > than helps, and I'mspeaking as a 'shared hosting' customer. What kind of solution do you have in mind? How are you handling CFCs on a shared environment right now? What kind of issues are you facing? ---------------------------- 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]
