Oh... don't misunderstand my comments. I'm responding from a position of complete ignorance on the topic. I just wasn't sure what the issue was that deploying CF in that manner would address.
Sounds to me that running multiple CF instances, each with a few sites/apps in each instance would be a good way to go under any circumstances to protect apps in others instances from an app that may lock up a particular instance. Sounds especially good to me, since usually just code my sites on my workstation and then just test and deploy straight on my production server. If I had multiple instances running, I could create a new instance for a new app and run it inside that VM/CF instance until it proved stable, and then transfer it to the "main" VM/CF instance. Does that sound like a reasonable approach? Rick -----Original Message----- From: Beru [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 10:48 AM To: CF-Talk Subject: Re: Managing multiple CF7 instances to one IIS site Rick, How would you make sure a CF application off the root of your web site does not interfere with another application on the same web site? I thought it would be logical to run each of these apps in their own instance... Is there another solution? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270474 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
