CFUNITED – The premier ColdFusion conference David Epler Constella Group Choices: The Other ColdFusion Servers

June 28 th – July 1 st 2006 The Choices  BlueDragon  Railo  IgniteFusion  Coral Web Builder

June 28 th – July 1 st 2006 BlueDragon Editions  Server (aka Free Server) Limited database and webserver connectors based on OS No support for HTTPS  Server JX  J2EE .NET

June 28 th – July 1 st 2006 BlueDragon Pros  Most widely used alternate CFML server  Been around for years, has good support and user community  Excellent documentation CFML Compatibility Guide CFML Enhancements Guide

June 28 th – July 1 st 2006 BlueDragon Cons  Perceived to be behind Adobe CFMX

June 28 th – July 1 st 2006 BlueDragon Resources  BlueDragon Interest List Archive  BlueDragon FAQ  BlueDragon Bug Tracking  Vince Bonfanti's Blog blog.newatlanta.com

June 28 th – July 1 st 2006 Railo Editions  Community Limited to one site per server, but free* Removed functionality  CFX tag support  Lucene search (cfsearch, cfindex, cfcollection)  Professional Licensed by # of sites served on server  Enterprise Unlimited sites per server, sandboxing

June 28 th – July 1 st 2006 Railo Pros  All editions can be deployed to any J2EE/JSP Servlet engine  Flash Remoting using AMF  Supports Fusebox 4.1, Mach-II, and ModelGlue  Fairly complete CF5/CFMX language support

June 28 th – July 1 st 2006 Railo Cons  Newest kid on the CFML block  Currently no support for webservices  Documentation is not as complete as Adobe or New Atlanta

June 28 th – July 1 st 2006 Railo Resources  Railo Documentation  Yahoo! Group

June 28 th – July 1 st 2006 IgniteFusion  Free*  Windows only CFML engine  Use IIS, Apache, or iPlanet  Documentation is in Windows Help File  Does not support frameworks (Fusebox, Mach-II, etc.)  No XML and WDDX support

June 28 th – July 1 st 2006 Coral Web Builder  More akin to CF Everywhere concept from Phil Cruz and Dick Applebaum philcruz.com/cfeverywhere/  Not a lot of information regarding CFML compatibilty on the site

June 28 th – July 1 st 2006 Getting Code to Run  Expect errors Most CFML engines strive to be as compatible to CFMX as possible Usually can fix with minor changes to code  Use the debugging output and logs to track down errors  Run code side-by-side in other CFML engine and CFMX to compare

June 28 th – July 1 st 2006 Getting Code to Run  Stay away from implementation specific tags and functions,,, etc.  Use support forums, lists, and Google Someone else might have already found the answer and posted it  Read the docs!

June 28 th – July 1 st 2006 Example: BlogCFC v4.03  Ray Camden's BlogCFC relatively prominent application deployed  Works out of the box for BlueDragon Minor previous gotchas  v4.0 had a function in blog.cfc called render() which conflicted with BlueDragon because it added a function called render()  BlueDragon uses a different RegEx library and behavior was slightly different from CFMX, fix was to modify the RegEx

June 28 th – July 1 st 2006 Example: BlogCFC v4.03  Railo 1.0 only required 1 change ping.cfc lines 74, 128, and 168 needed name=”xmlStuff” added to the Railo treats the name attribute as required although it is optional for CFMX and BD when type attribute is body or XML

June 28 th – July 1 st 2006 Thanks  Q&A  Contact