Well i must say, so far i am impressed with ColdFusion 10. They have really done a large overhaul to its base along with many new features. One thing i am impressed with is that adobe has replaced the older antiquated JRun subsystem that CF use to run on with Tomcat. Tomcat is notably more enhanced then JRun when it comes to an application built on Java. The draw back is that the structure of the new CF is very different from the older versions, especially when it comes to multi instance applications.

Adobe has tried to keep things as similar as possible, but one thing i noticed is that when installing a multi instance server, you no longer have that option on the initial install. You will have the option to install CF 10 initially, then if your license supports multi instance, you will then have the option afterwards to install another instance. Now onto the part that i have been heavily interested in.

One thing that was an enormous draw back on earlier versions of CF was that when you installed multiple instances for separate applications, you had 1 JVM config file that was shared between all instances. Now what does this mean?. Well it means that any memory adjustments or class file inclusions you made, applied to all instances. So this was not truly segmented if they all shared 1 file. I always believed that multi instance applications should be completely autonomous, and nothing should affect the other instances. Else this really defeats the purpose of having separate instances. So on we go, in older versions it was not impossible to have separate JVM config files for each instance, it was just a pain in the rear to remove the service and re install it while assigning the service to a new JVM config. CF 10 has inherited this idea and has truly segmented instances from one another. It was very confusing to me because i was use to all instances sharing the same bin and lib folders in the root. Well in CF10 each instance is listed in the root folder of CF10 as it’s own folder and under that having it’s own JVM and file structure. This makes each instance totally autonomous. Awesome!.

Another advancement has been to their schedule task manager. Anyone who know me, knows this drove me nuts. Previously when tasks failed, you would never know unless you trapped for the failure in your task. And the logging for these tasks were vague at best. Well they have completely redone this aspect and given Schedule Task Manager a true face lift with some pretty cool features. So i encourage all you CF geeks out there, give the below link a look and leave your comments on what you think of the new and improved version of CF. Happy coding!!.