I have been reading up some on CFMXJ2ee for a client who will likely host his own site and sites of his customers. He is considering outhouse hosting, for about a year, then the economics should justify bringing the hosting inhouse. The platform will likely be Linux or Unix.
According to what I have read, with CFMXJ2ee he could run a CFMX server context (instance) for each site -- or even for each application within a site -- and this should perform better than a single CFMX Standalone server. This would isolate each site from the others, I haven't seen it mentioned, but wouldn't another advantage be that each context would be able to use "dangerous" CFMX features such as cfobject, custom tags, etc., because the contexts are isolated. If this is true, wouldn't you expect that shared-host providers would use CFMXJ2ee instead of CFMX Standalone -- better performance, more features, less security exposure? Couple of questions, from a shared-host perspective? Do multiple contexts outperform a single, shared context (standalone server)? Is there any performance data or experiences available? Is there a practical limit on the number of CFMX contexts that can run concurrently on a app server like JRun? Given the same hardware, how would/should this compare to the number of users that could share a CFMX standalone server? Am I missing any other limitations/advantages of CFMXJ2ee for shared-hosting? TIA Dick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
