Nando,
thank you for your detailled response!
I'll try to sum up my thoughts about it...
> "application scoped" instead of "server scoped". And if you think
> about it a
> moment, it makes complete sense, because 98% of the time, a mapping is
> relevant to an application only and not to the whole server. That's a
> guesstiimate, but i think it's often the case.
Well, I can not confirm that, at least not from my experience, which of
course, does not cover all possible situations. ;-)
> At present, one of the "best" workarounds to
> avoid using a "server scoped" mapping - for the purpose of code
> portability - seems to be to put all of your CFC's and any code that
> calls them in the root directory of your application, which is a
> horrible workaround.
I don't see any need to put all CFCs in the root directory... I have
mine organised in folders and do not have a problem with it. (I do
development on my machine where I have many apps of different clients,
and when I deploy to a clients machine with a different root directory,
I simply change a few variables..) But then, I use BlueDragon and am
able to use variables in e.g. extend paths (as mentioned in my other
mail) and, I must admit, I rarely use CF for OO development.
for me, the really big advantage in the bigger picture is it would allow me
to simply and easily package a product that is meant for distribution and
deploy / host many instances of that app on a webserver, without needing to
change the codebase each time and test each of them to make sure i haven't
introduced any bugs. I can do that for 20 or 30 or 40 installations, but a
business model that requires 100's or 1000's of instances of the app is
going to be increasingly difficult to support.
If you do not want to maintain many installations, that means all
instances are in the same directory, right? Then what would be the
problem with a server wide mapping that applies to all clients?
i could work on different variations of the same codebase on my dev machine
without needing to change the mapping in over 1800 places in my codebase. I
can't believe there are that many references to the main mapping i'm using
in there, but there are! and i need to sometimes quickly work up variations
and try different branches out. my best workaround right now is to set up
multiple dev environments so that my branches aren't filled with
different-yet-same code, but that takes time.
As I do not know your setup or your code, so of course I can not make
sensitive comments about it...
Of course, if i were working in a one app per server corporate environment,
server scoped mappings would likely be perfectly sufficient. But in smaller
shops developing apps to deploy multiple times, it seems many of us are
running into a rather urgent need for application scoped mappings (or to
drop the use of mappings entirely, and make whatever sacrifices are
necessary).
Again, I do not know your setup, but to me it seems it should be
possible to deploy a shared app only once... unless of course clients
require code customization.
Best,
Chris
----------------------------------------------------------
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).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
