Railo was created by the Swiss company Railo Technologies GmbH, intended as a high performance alternative to Adobe ColdFusion. In 2008, Railo switched to an open source community-driven model, and became a JBoss project. The Railo Open Source project is led by Railo Technologies, with development work funded by consulting and support contracts, but anyone may contribute code for consideration.
Naming
Railo was named after an alien dog in Star Trek: Enterprise. The dog is actually named Rhylo, but written phonetically in German it is Railo.[1] Thus, Railo can be pronounced either as rhy-lo or as rai-lo - both are acceptable.
Railo major releases have a codename of notable and loyal dogs from history.
History
Railo began in 2002 as a student project by Michael Offner and Gert Franz to compile CFML code into PHP, a choice made due to the ubiquity of PHP, however it was found that this did not give the desired performance and stability, and the decision was made to switch to the Java platform instead.[1]
The project was successful enough that it was decided to continue to develop into a full product. Several alpha and beta releases were made before the official 1.0 release in April 2006. Railo continued to be developed but was relatively unknown to many CFML developers, until June 2008 at the Scotch on the Rocks conference in Edinburgh, when Railo Technologies used the Day 2 keynote to announce a partnership with JBoss and a switch to open source.[2]
In May 2012, at the cf. Objective conference, the foundation of "The Railo Company Ltd" was announced, a Private Limited Company, comprising the Swiss company Railo Technologies GmbH in conjunction with five other companies who operated in the CFML industry.[3]
Lucee Fork
On 29 January 2015, the Lucee project, a fork of the Railo 4.2 codebase, was announced by the original developer of Railo, who stated that he would not be working further on Railo. The other developers have confirmed they will also be focusing solely on Lucee, and - although no official statement has been made by The Railo Company - the community consensus is that further development on the Railo project is unlikely.[4][5]
On 19 July 2016, The Railo Company was dissolved.[6]
Release history
Major version (Codename)
Minor version
Release date
Notes
0
Alpha 1
2004-04-10
The first official release of the Railo CFML engine.[7]
Alpha 2
2004-05-18
Alpha 3
2004-08-03
Alpha 4
2004-10-21
Beta 1
2005-01-16
The first beta release of Railo.
Beta 2
2005
Beta 3
2005
RC1
2005-09-23
The first release candidate of Railo was presented to the German CFUG in Munich.[7]
Railo has an installer for Linux, macOS, and Windows, which bundles Apache Tomcat. There is also a pre-configured Railo Express download using Jetty.
From v4.0 onwards, Railo will have a command line version, enabling CFML to be used as a general-purpose language, outside of the servlet environment.[10]
Railo since v3.1 is licensed as LGPL v2.1,[11] with the source code available on GitHub[12]
Philosophy
A primary aim of Railo was to provide the functionality of ColdFusion using less resources and giving better performance, and the Railo Technologies team continue to "treat slowness as a bug" as a core development philosophy. Many performance tests have shown Railo to perform faster than other CFML engines.[13]
In addition to this, Railo attempts to resolve many inconsistencies found in traditional CFML. These are either forced changes in behaviour, or configurable options in the Railo Administrator.
The Railo Technologies team have always been open to feedback and active at CFML community events, and are keen to remind people that Railo is a community project.
Railo Technologies also creates strong technology partnerships with CFML software companies, including Blue River Interactive Group (developers of Mura CMS), CONTENS Software GmbH[14] (developers of CONTENS CMS), and Intergral GmbH[15] (developers of FusionReactor and FusionDebug), to help ensure their software works well with Railo. In addition, Railo Technologies offer formal "Partner Programs" for Solutions (development), Hosting, and Training.[16]
Event Gateways for asynchronous code execution[34]
Native support for a variety of different caching mechanisms[35]
Native session management (CFML sessions or J2EE sessions) with onSessionStart and onSessionEnd triggers.
Built-in user authentication and roles functionality.
Security
CFML has built-in functionality for preventing code injection, via the cfqueryparam tag, and functions such as HtmlEditFormat, XmlFormat, JsStringFormat.
There are also third-party CFML implementations of the OWASP Enterprise Security API,[36] and the AntiSamy project.[37]
One of the key architecture decisions with Railo was to follow the JEE servlet model, with support for multiple independent web contexts on a single server. This is a key security factor, as it prevents unrelated applications from interfering with each other, as may happen on a shared ColdFusion server (which only has a single web context).
Syntax
Railo implements the CFML language - see the CFML syntax section for examples as well as CFScript.
Differences
Differences from other languages
CFML has a tag-based syntax which is visually different from most other languages, though aside from this it is similar to other dynamic languages, with the following exceptions:
CFML contains two syntaxes, a tag-based syntax (not XML compliant) and a C-style syntax called cfscript.
Arrays in CFML are indexed from one, not from zero.
CFML supports both ordered and named function arguments, or a combination.
CFML does not have static variables.
Differences from Adobe ColdFusion
Whilst Railo implements CFML, and is generally compatible with Adobe ColdFusion (ACF), the original CFML engine, there are some notable differences between the two:
Railo uses a multi web context architecture, compared to ACF's single web context.
Railo allows you create "built-in" user-defined functions, using standard CFML.
Railo is unable to decrypt (or execute) templates that have been encrypted with ACF's encryption mechanism.
Railo has a significantly faster release cycle for major, minor, and patch releases.
In Railo, scopes always take priority. In ACF, creating a variable named "Url" may block access to the Url scope. In Railo, the variable can only be accessed as "Variables.Url".
Railo only searches for CFCs inside the custom tag path if defined accordingly in the administrator (it has a distinct CFC path instead).
Railo 4.x introduces a command line interface (CLI) that allows executing CFML scripts from the command line
Railo allows using object methods. So instead of using array Append (arr, "value") one can write: arr.append("value").append("anotherValue").
See also
Lucee - fork of Railo currently supported by Railo's original developers.