I had read on the Railo Mailing list that Transfer now works on the latest release of Railo 3.0.1.000. So I went to check it out and loaded up the TBlog example app that comes with Transfer and much to my amazement it loaded up between 3-5 seconds (with Debugging on). I went and fired up the same app on CF 8 and it took 25-30 seconds (with debugging on as well). I know that having debugging turned on (Especially with CFC's) really slows down CF serve and is in no way indicative of how the app will perform in production. That, and that there is a significant performance cost when the CF server (re)creates the Java classes...
But Daaaaaa-yum! That is almost a ten fold difference. And when I am developing I almost *always* have debugging on.
I have also been testing a lot of apps (mine and others) on Railo to see what works and what doesn't. So far so good. The only significant problem I have had was with how Railo handles Structures on Rick Roots ColdFusion File Manager (CFFM). But other than that, most all of the apps that are part of my day in day out work day work flawlessly with Railo.
Oh yeah, the latest version of Railo supports CFAjaxProxy. That SO ROCKS!!!
Way to go Gert, Michael and the rest of the Railo Crew! I CANNOT WAIT to see Railo 3.1 on Nov 28.