What do you guys think?

It seems like there are several questions that are both related and unrelated to the thread at hand depending on perspective.

1. Should CFCs be better supported in shared hosting environments?
Yes, of course! It appears you have already found some ways of dealing with shared environments, but let me point out a couple of others.


First, I shared code a while back when CFMX was first released that showed how to instantiate a CFC using a relative path. This code used internal CFMX classes, so I am not sure if it still works, but I am sure that there is a way to do it with CFMX 6.1 even if the code I shared no longer works. Maybe cfobject/CreateObject() should support relative paths for components.

Second, if hosting providers would create separate instances of the application server for each customer that would remove this problem. I have stated before that I didn't think doing this with CFMX was economically viable, but now that BlueDragon is going to support CFCs, shared hosting providers have an opportunity to fix many headaches in the shared hosting world.

2. Should mappings be configurable on a per application basis?
I would think that would be useful. I also think it would be nice to separate the paths used for custom tags from that of CFCs.


3. Should CFCs be fully dynamic?
That is a much harder question to answer. Doing it just to support mappings surely is not a good reason, but there may be some benefits to CFCs being fully dynamic. I think the key is to find applications that would make use of fully dynamic CFCs and then we could look at whether there is a benefit to doing so.


Matt Liotta
President & CEO
Montara Software, Inc.
http://www.MontaraSoftware.com
(888) 408-0900 x901


----------------------------------------------------------
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]

Reply via email to