.cfmfiles in this folder. (The empty
Application.cfctakes care of that.) Also, no URL rewriting will be performed in this folder, so it's a good fit for placing CFCs that need to be accessed remotely via
<cfajaxproxy>and Flash AMF binding, for example.
Wheels.cfc. You can place functions inside
Controller.cfcto have that function shared between all the controllers you create. (This works because all your controllers will extend
Wheels.cfcis an internal file used by Wheels.
sendFile()function should be placed here. Even if you don't use that function to deliver files, this folder can still serve as file storage if you like.
Application.cfcfile in here, which will prevent Wheels from taking part in the execution.)
<cfajaxproxy>in your views to bind directly to a CFC as well.
Application.cfcin those directories. Otherwise, Wheels will try to get itself involved with those requests as well.