I see a big issue with rewriting files at install time. The issue isn't the mapping. (Although that does limit your sales to someone who has enough knowledge to understand what a mapping is and what you are telling them to do during install. Portability is more than how a piece of code runs... what you are saying is the code isn't portable.)
Aside from that, there is also the issue that some hosting environments lock down directories so that the code cannot write files without you requesting them to manually add CF permissions to write, update files in those directories. (Sandbox security) This is just a fact (and I have debated the policy with some of those companies personally.) John Farrar -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barney Boisvert Sent: Sunday, September 11, 2005 1:36 AM To: [email protected] Subject: Re: [CFCDev] Factories and mappings You've got one thing backwards, subclasses would need to be at the same level or HIGHER than the class they're extending. Other than that, it sounds reasonable. However, there's absolutely no reason that any hosting environment (dedicated, shared, mass hosted, whatever) shouldn't give each individual website at least one mapping, so I'd say you're better off with a build process that'll do a substitution of that mapping at install time. So you're code would be say extends="${cfcRoot}package.cfc", or whatever, and then at install time, you run the build script and it subs out ${cfcRoot} with the appropriate value. I'm also kind of curious. How large of applications are being mass hosted like this, and need to have the ability to play nice with myriad other apps (both the same code and different)? It seems to me that the apps large and complex enough to really benefit from a massively OO backend probably aren't the kinds of apps that get deployed a bunch of times to shared servers. cheers, barneyb ---------------------------------------------------------- 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]
