this is already the case, Railo has features that CF does not or which work differently, however there are some settings in the Railo admin that allow you to set backwards compatibility with CF. If you want your app to work on all platforms then you need to use code and syntax that works on all of them and avoid using tags, functions and attributes that are platform specific.
On Mon, Mar 5, 2012 at 8:18 PM, Brian Thornton <[email protected]>wrote: > > I understand the timelapse from Adobe release of a function of CF to > the time Ralio allows it. But I wonder what happens when they start to > allow for separate features. > > Like for instance, cfparam as part of a cfscript is allowed in Ralio. > Say you write this and then port the code over the Adobe friendly CF > machine no ralio, what happens if Adobe then later allows that code > functionality in a different way then ralio and the changes it.... > > Should/Would Ralio work like Adobe new or should it work like Ralio old or > both? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350234 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
