Bill, that's what Nando is not describing. My interpretation was that every install had a complete copy of the code, not just the custom code and then access to shared-use components for the core functionality. I very much like how you've set up your app, and have done it exactly the same way myself. It's also the way Mach-II and FB4.1 are designed to function (single core install shared by multiple apps).
cheers, barneyb On 9/11/05, Bill Rawlinson <[EMAIL PROTECTED]> wrote: > Barney, > > To answer your question: > "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)? " > > the company I work for builds an app that, against our recommendation, > is often installed many, many, many times (in one instance 300 times) > on one server. It is a pretty complex app but we have architected it > in such a way that the core files that are the same across all > instances are installed in one location using using a standard named > mapping. Then only the subsets of code that are unique for each > instance are "duplicated" for each install. > > The app is kind of a CMS/Portal/Intranet/Knowledge Management/Document > management hybrid that can be extended fairly easily to integrate with > other applications. Written almost entirely for CFMX 6.1 with CFML > though there are some small parts in Java when the functionality was > needed. > > Sure, we would love it if every customer were willing to deploy on > seperate servers (or at least with seperate CF instances) but that > generally isn't the case even when dealing with our larger customers > (those who deal in the billions of dollars). Since our app CAN work > sharing resources across many intances, even if performance becomes > degraded, the customer often will do that in order to save $$. > > > > Bill > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- 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]
