My only reason for avoiding this directory structure in particular is because a lot of hosting providers set their clients web accounts up where their only access to FTP is within their web root, so they can't really place files outside the web root. Now -- I may not personally have this problem, but I try to design software that's generic enough that even people using shared hosting accounts could conceivably use it ( 'cause then they could conceivably buy it ;P ), and with many shared hosting providers this structure isn't really feasable.
So for me it's better to avoid this as a possible limitation, 'cause I'm inclined to think that by and large people are liable to purchase an alternative product for their existing hosting, rather than change their existing hosting to use my software. This also makes MX a really good thing for me moving forward because of MX's improved sandboxing likely meaning that many CF hosting providers will no longer disable cfdirectory and cffile which my applications definitely need. S. Isaac Dealey Certified Advanced ColdFusion 5 Developer www.turnkey.to 954-776-0046 > 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 Get the mailserver that powers this list at http://www.coolfusion.com
