Application.cfm is a file that runs on every cfm page. Anything you do that should be done on every page can be moved to the application file.
If you want to keep the display code separate from the logic, use an include or a tag to display it, but feel free to put it in there. I see no reason to clutter every page of a site with something that can be done once in a single file. Once the "something" becomes conditional (not on every page), then you need to decide how much conditional code you want to run in the application file. But site-wide headers and footers, and even logging, make good sense in the Application/OnRequestEnd. IMHO. On 12/30/05, Matt Robertson <[EMAIL PROTECTED]> wrote: > I would never use Application.cfm for output. As far as I'm concerned > its strictly for internal-use code. So I wouldn't use raw html OR an > include. I would use the include on my display template. I regard > Application.cfm as part of the processing tier of an app, not the > display tier. > > I would say that while doing this is certainly possible its the wrong > tool for the job. > > -- > --mattRobertson-- > Janitor, MSB Web Systems > mysecretbase.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228000 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
