Anyway, an alternative to including all the application.cfm files all the way back up the tree would be to stick with application.cfm file in the root directory and have files in the sub-directories called something like applicationInit.cfm. Then in application.cfm (in the root) I would traverse down the tree including the applicationInit.cfm file - if they existed. That way your entry point is always the same and in your applicationInit.cfm file you can safely assume that your application has been defined. If you work bottom up you're never quite sure...
Just my $0.02 worth...
Brett B)
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
each application.cfm includes the one above
Just looking for some feedback I have not thought of yet ...
--
Taco Fleur
Senior Web Systems Engineer
http://www.webassociates.com <http://www.webassociates.com/>
---
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/
-- Brett Payne-Rhodes Eaglehawk Computing t: +61 (0)8 9371-0471 f: +61 (0)8 9371-0470 m: +61 (0)414 371 047 e: [EMAIL PROTECTED] w: www.ehc.net.au
--- 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/
