Railo Roadmap

We have been asked a lot about releasing a Roadmap for Railo so that users can see what is coming and when is it coming. In Gert's presentations this year he will go deeper into the details of the different features. Here's a list of the currently planned and implemented features for Railo 3.3 and Railo 4.0.

Railo 3.3 - codename: Hachiko

http://en.wikipedia.org/wiki/Hachiko

  • ORM (final)
  • Gateway (final)
  • Image Filters (150 different image filters)
  • Cache based storage for Client Scope
  • Storage support for Session Scope

Railo 4.0 - codename: Appollo

http://en.wikipedia.org/wiki/Appollo_(dog)

  • Extend Java - it should be possible to extend a Java class/interface inside a CFC and then this CFC is checked against the class interface and can also be used inside Java as this type of class
  • RAAS (Railo As A Service) - Run CFML outside Servlet context, you can execute Railo in every Java App without having a SERVLET ENVIRONMENT
  • Closures - We will be proposing this to the CFML Advisory Committee for the next specification and we will produce a reference implementation for user feedback.
  • Image handling - improve image features
  • Scheduled tasks - improve the functionality and introduce new behaviour
  • CFScript extension - cfscript language java
  • Installation - Better / Official Installers
    • Railo based installers - Railo Extensions that can install Railo on a system, i first get a Railo Express then you install Railo from within the admin

Additional features under consideration for Railo 4.0 (high priority):

  • PDF handling - improve pdf features
  • IDE support - CFEclipse with Railo included
  • Clustering - Allow storing the application, server, session scopes in the Cache, similar to client scope (client scope is always in memory for around 5 minutes, after that it is written to the persistent layer and removed from memory)
  • Admin API - a collection of cfcs that allows to manipulate the configuration
  • cfretry
  • BlazeDS Upgrade - 4.0
  • Add an Error template
    • This error template should contain a list of related solutions found on the net
    • Perhaps regular google search is the easiest implementation
    • A Google group search and a JIRA search perhaps as well
    • Allow disabling this feature in the template itself
    • Allow adding an own solution to the central solution DB (located at Railo)
  • AIR application or CFBuilder Extension - for creating Extension Providers / Managing the XML file for Extension Provider Apps / Plug-ins.

Additional features (lower priority):

  • replace soap communication with a faster binary communication when on both ends is Railo
  • cfvideo
    • improve update cfvideo
  • Output Buffer
    • Native ability to interact with the output buffer: clean it, append, preppend, get contents, etc - this is only possible when cfflush was not used
  • Coding
    • Create the possibility to check how much of a query has been used (what columns, which rows) Maybe something for the debugging output. This would output something like: queryname whatever records 34 time 242ms usage 26% <details>
  • Propose code optimizations
  • Abstract function
  • Query coverage
  • Autotuning
    • Autotuning (or proposals for tuning, like when the server is often running low on memory propose to increase the memory...)
    • If Autotuning is turned on, then Railo checks for certain things:
      • Select *
      • More than X records in a query
      • very much time lost in certain loops
      • lock collisions
      • other things
  • null support
  • New Tag <cftimeout time="60" throwOnError="true">

Not Allocated to a release:

The following features may be allocated to 3.2, 3.3 or 4.0 or may be deferred until a later release (depending on workload and effort involved).