> On Sunday, Mar 30, 2003, at 13:15 US/Pacific, S. Isaac > Dealey wrote: >> If you do store application settings in xml they really >> should >> be stored in a .cfm template so that the CF Server will >> protect the >> data >> from someone attempting to get at it from typing a URL >> into their >> browser,
> Why not put it outside the webroot? That's an option certainly. I don't like to put anything that's a part of my application outside of the application's root directory because of the potential for problems if the app gets moved, etc. It also means that if you sell the application, you have to give instructions for installing it that include storing that data outside the webroot, or part of the installer has to ask the person installing the application where outside the web root they want to store the settings file. So those are my reasons for prefering not to have core templates or files outside the web root. I have similar reservations about using the custom tags directory. >> <cfset fuseaction = >> rereplacenocase(fuseaction,"[^[:alnum:]]","","ALL")> >> <cfinclude template="#fuseaction#.cfm"> >> >> Which is both less code and faster -- the only >> disadvantage is that >> you can >> no longer perform a multi-file search through your >> application for >> "foo.cfm" >> and produce this page, you would have to search for >> "foo". > And it also ties fuseactions to filenames which is > kinda against the whole point of FB. It lets you > abstract all of the file system structure and names > away so that the URL interface you present to your > users is consistent. I don't understand how the mechanism for including files would change the user interface any... Unless you're talking about giving people url's that go to /root/fuseaction/index.cfm which isn't actually what I was suggesting (although I realize my verbiage may have been a bit confusing). In any event, a directory containing files or subdirectories is rather a lot like a <cfswitch> satement in that, you can only have one instance of any given <cfcase> just as you can have only one file or subdirectory with a given name. On *nix of course you have to make sure that the directory / file names are all one case (I prefer lower) to prevent someone accidentally mangling the case when typing in a URL with a fuseaction in it. s. isaac dealey 954-776-0046 new epoch http://www.turnkey.to lead architect, tapestry cms http://products.turnkey.to tapestry api is opensource http://www.turnkey.to/tapi certified advanced coldfusion 5 developer http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
