Ben Forta wrote: > > Regardless, it is worth noting that problems caused by the lack of > locking (CF4.x and CF5) can be slow and gradual. On a shared box you may > see memory corruption problems (do to the lack of locking) even if your > app has no shared scope variables at all. How? If another app on the box > uses shared scopes and fails to lock code. All CF apps share the same > instance. > > Which is why CFMX on J2EE is so compelling. Each app runs in its own > safe little world.
If only running a few hundred instances wouldn't require a mainframe... Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
