Just remember it should always be called "Application.cfm", not application.cfm - same goes with OnRequestEnd.cfm. Why MM have stuck to this after nine years is beyond me but that's the way it is.
Peter Tilbrook Manager, ACT and Region ColdFusion Users Group - http://www.actcfug.com 4/73 Tharwa Road Queanbeyan, NSW, 2620 AUSTRALIA Telephone: +61-2-6284-2727 Mobile: +61-0439-401-823 E-mail: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Taco Fleur Sent: Tuesday, 21 September 2004 5:19 PM To: CFAussie Mailing List Subject: [cfaussie] Re: Include application.cfm Robin, I don't like the way you think at all!! ;-)) To much like the way I think (in this case anyway), its actually sort of like I have it, but *slightly* different. Taco Fleur Tell me and I will forget Show me and I will remember Teach me and I will learn > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Robin > Hilliard > Sent: Tuesday, 21 September 2004 3:56 PM > To: CFAussie Mailing List > Subject: [cfaussie] Re: Include application.cfm > > > 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/ > --- 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/ --- 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/
