we use mappings without a problem. Our product is often installed many, many, times on the same server. In fact one client installed it
100 times on one server (against all advice to the contrary).
The cfc's are all inthe same place. the same mapped location. All of the applications share the same set of cfcs. It was a big part of why we went to a mapping. So we could take all of the duplicated code that was sitting in each applications "components" directory and not have to deploy the same code to people, (100 times).
There are some negatives to this approach. If a patch goes out that actually breaks something then all 100 sites get broken at once. Of course, the counter is true. If a patch goes out they fix all 100 at once. Our customer is willing to assume the risk in order to avoid going through upgrade process for every instance on a single server.
We don't have any customers that are trying to run an old copy of the app and a new copy on the same server (unless they are running one pre consolidation of CFCs and a current copy). So this setup works out pretty well.
In our experience mappings as they are have worked fine. I hope, that if they add application specific mappings, that they also keep the current global mappings available as well.
On 4/30/05, Dave Merrill <[EMAIL PROTECTED]> wrote:
Thanks everyone for chipping on this. Seems like we're all landing in about
the same somewhat disappointing place.
For instantiation paths, various techniques work for pointing to an
app-specific cfc directory. I personally have settled on having the root
application.cfm set application.app_root_path from cgi.script_name when the
app starts up. Instantiation paths are based off that, so far in
/_assets/class/. That means no location-specific recoding is needed on that
level (unless the app is moved while it's running ?!?). I use a generic
method to return instances based on that setup.
However, there's no good solution for app-specific inheritance trees:
- You have to code your classes' inheritance trees to a known path mapping
for that app.
- That's true even for multiple instances of the same app on the same
server -- each of them has to have a distinct path name if you want to keep
their classes separate. Because of that, you have to modify the actual
classes in each instance to use the map name for that instance.
All told, it's not so pretty, especially the multiple instance scenario. I
hope Adobromedia sees fit to enhance CF in this area; it's got a bad damage
curve, where the larger the scale of deployment, the worse the problem is.
Dave Merrill
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
--
[EMAIL PROTECTED]
http://blog.rawlinson.us
If you want Gmail - just ask. ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
