You may have noticed during installation of CF 10 (as with previous releases) that you are offered the option to either connect CF to an external web server if you have one installed (such as Apache or IIS), or you can use an offered “built-in web server” (or what is also sometimes referred to as the internal web server).
That’s not really new news, as the same option was offered in CF 6-9. But there are some new things in CF10 to consider about that option, and that’s what I’d like to share here.
First, I want to show how if you chose NOT to enable the built-in web server, you CAN enable it after the fact, with just a simple modification to a single xml file (which is a different one in CF10, and I want to show where that is, share some tips on changing it, and point out where to learn more.)
But there are also still more things about the built-in web server that you can control, which you may not readily discern even from the docs, and I provide here additional info with respect to that.
Finally, while in previous releases the built-in web server (which was really the JRun web server) was something generally regarded (even warned in the installer) to be used only for development and testing, the built-in web server in ColdFusion 10 is in fact the Tomcat web server (Coyote), which is a much better web server out of the box, so you may want to consider it even for production.
I realize that last point will be “pushing it” for some. Hey, I’m not saying that you should change anything, just letting you know that some might reconsider things. Hear me out, please. I’m just sharing documented info that might not be so readily found about a relatively new subject for the CF community (so don’t shoot the messenger!)
Read the entire article here.