Out of curiosity, I decided to dump the client project I'm working on just now into the current Railo 2 Release Candidate.

We're currently developing on CF7.0.2 and using SQL Server 2005 as the database.

So, what was the prognosis?

No code changes were required. It just worked.

It's about 3 times as fast on Railo. No scientific numbers for you. It's just that when I reinit the app, I can usually get up, walk round the office, and when I sit down again, the app is now being served up.

With Railo I only got as far as getting out of my chair.

Pretty damn impressive. Now to see how it goes on CF8.

With Ben Forta's announcement in regards Per Application Mappings, it brought up the topic of "How is it being done across the different CFML engines?"

<CFMAPPING> was introduced in BlueDragon 6.2.1, whereas in Scorpio Per Application Mappings will be supported via Application.cfc

Reading a blog posting from Vince Bonfanti from a while back, it looks like NA plan to introduce support via Application.cfc as well (at the time BD didn't have Application.cfc).

The nice thing about NA's implementation is that older applications which still use Application.cfm/onRequestEnd.cfm will have support for the Per Application Mappings ...

And I believe Railo supports Per Application settings as part of it's core architecture. See the following blog post by Gert Franz

It's all good stuff, though maybe not exactly compatible across all the engines.

So, who's approach is best? What are the pitfalls of each?

Why not come along to Scotch on the Rocks, where we have folks from Adobe, New Atlanta and Railo and ask them directly.