Taco,
No problem, I do it often. Two random thoughts about this:
- I put my base application.cfm in the directory above my webroot - it's possible this way to build a cf application with no actual cf code under the webroot if you want to take it to the extreme. All you need under the webroot are empty files with cfm extensions for each browseable url. All your code can be off under your cfmappings, called from some front controller logic in application.cfm. Good for security, not saying this is at all a best practice but knowing it's possible can change the way you think about structuring your apps.
- Sometimes I think of the directory hierachy as a class hierachy of request types, with application.cfm as an init method for that "subclass" of request. Including the parent application.cfm is like calling super.init(). Following that analogy you should probably make it a rule to always call the parent application.cfm first - it's required in OO languages, so someone's run into whatever happens if you don't.
Food for thought anyway.
Robin http://www.rocketboots.com.au
Taco Fleur wrote:
Any reason not to include application.cfm in another application.cfm?
Currently I have something like:
web/application.cfm
web/object/application.cfm
web/object/function/application
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
