Hi guys, > I agree. CFMAPPING would be more-flexible than another attribute in > CFAPPLICATION. If this is finally implemented in CF, I certainly hope > the values allow for dynamic variables and not just hard-coded values.
I have followed this thread not too closely, and maybe this seems like a dumb question, but.... what is the big advantage of per application mappings?
If you only want to access resources within the web root, you could simply use variables that contain paths (which you all do in one way or other, I feel sure).
But, if you want to access resources outside the web root, wouldn't that be a security risk? Imagine a hoster with x clients, where each client could define mappings and data sources and thus could access other clients' data sources or maybe even system paths?
I think that if you offer such a feature, there also must be the possibility to disable it in the admin interface.
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]
