Or you could just place those files outside of your webroot. Then you could
name them whatever you want. For example, a lot of our site's are organized
like:
\SiteName
\Collections
\CustomTags
\Database
\Documents
\Source
And \SiteName\Source\ is established as the webroot. Obviously, you could
very easily add an Includes, UDFs, or any other directory outside of the
webroot.
--
Mosh Teitelbaum
evoch, LLC
Tel: (301) 625-9191
Fax: (301) 933-3651
Email: [EMAIL PROTECTED]
WWW: http://www.evoch.com/
> -----Original Message-----
> From: Matthew Walker [mailto:Matthew@;cabbagetree.co.nz]
> Sent: Wednesday, October 30, 2002 3:32 PM
> To: CF-Talk
> Subject: RE: new to CFSCRIPT
>
>
> > I agree with the descriptine file names, etc., but what's
> > wrong with naming
> > it *.udf?
>
> People could download and view your UDFs. I've even used .cfm extensions
> on xml files for that reason. I also have a system in place where any
> file with a 3-letter prefix and underscore (e.g. act_deleteaccount.cfm)
> cannot be run directly. You do this by placing
>
> <cfif REFind("/..._", CGI.SCRIPT_NAME)>
> <cflocation url="">
> </cfif>
>
> in application.cfm . This is similar to a technique in fusebox where you
> force everything thru index.cfm .
>
> Matthew Walker
> http://www.matthewwalker.net.nz/
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk
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
