Makes perfect sense, Ben. Goes right along with what I mentioned as a possible benefit in an earlier post... isolating apps that are new and need time to prove that they're not going to lock up the system.
Having the new apps isolated in an instance for awhile from other proven apps seems like an excellent idea. And, if I understand CF licensing issues correctly, I wouldn't have to purchase a license for each instance, right? Rick -----Original Message----- From: Ben Forta [mailto:[EMAIL PROTECTED] Sent: Thursday, February 22, 2007 10:56 AM To: CF-Talk Subject: RE: Managing multiple CF7 instances to one IIS site Rick, load balancing and performance for starters. But also, for better use of server resources. For example, I regularly see people running a single ColdFusion instance on a big fat box with 4 or 8 Gig RAM, memory that ColdFusion can't use because of limitations as to what the JVM sees. In such a situation having multiple instances makes lots of sense. I am also seeing more examples of multiple instances being used to isolate specific parts of the same single app, perhaps administration and internal facing stuff on a separate instance so it does not interfere with public traffic, or scheduled tasks and bots in their own instance, and so on. --- Ben ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270477 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
