Correct. And you should read what I wrote. I addressed your words, exactly.
On Tue, Nov 26, 2013 at 3:09 PM, Eric Roberts < [email protected]> wrote: > > Matt...please read what you quoted and that should address your statement > about non-cfm files... > > >> > >> Philip...it is in a .cfm file that handles the header. in this specific > >> instance, it is calling up a logo image in the header. If this was in > an > >> html file, then they would be correct...but in a cfm file...everything > is > > >parsed. > > > > >I know you've been told this repeatedly and so I'm probably just wasting > my > >breath (finger energy, I suppose), but you are 100% incorrect. 100% WRONG. > > >Here's a 100% accurate statement that is based upon your 100% inaccurate > >one: > > >CF does not execute html files unless your web server is specifically > >custom-configured to do so. In a default CF installation, CF only executes > >*.cfm(l) and *.cfc files. At no time does CF parse the entire file that it > >executes, but rather, it relies on specific syntax and code constructs - > >CFML and/or CFScript - to determine its parsing boundaries. CF never has > >and never will parse HTML. Period. > > > Please read before commenting. I clearly stated that it was in a cfm > file...not an html file...sheesh > > Eric > > > On Tue, Nov 26, 2013 at 2:07 PM, Eric Roberts < > [email protected]> wrote: > > > Matt...where did I say I was executing a non-cfm file? > > > > > > On Tue, Nov 26, 2013 at 2:04 PM, Matt Quackenbush <[email protected] > >wrote: > > > >> > >> On Tue, Nov 26, 2013 at 2:52 PM, Eric Roberts < > >> [email protected]> wrote: > >> > >> > > >> > Philip...it is in a .cfm file that handles the header. in this > specific > >> > instance, it is calling up a logo image in the header. If this was in > >> an > >> > html file, then they would be correct...but in a cfm file...everything > >> is > >> > parsed. > >> > >> > >> > >> I know you've been told this repeatedly and so I'm probably just wasting > >> my > >> breath (finger energy, I suppose), but you are 100% incorrect. 100% > WRONG. > >> > >> Here's a 100% accurate statement that is based upon your 100% inaccurate > >> one: > >> > >> CF does not execute html files unless your web server is specifically > >> custom-configured to do so. In a default CF installation, CF only > executes > >> *.cfm(l) and *.cfc files. At no time does CF parse the entire file that > it > >> executes, but rather, it relies on specific syntax and code constructs - > >> CFML and/or CFScript - to determine its parsing boundaries. CF never has > >> and never will parse HTML. Period. > >> > >> > >> > >> > The point behind having mappings is so that in the code, you are > >> > refering to a directiory by name rather than having to deal with what > >> the > >> > path is from the file. > >> > >> > >> > >> You are correct that by setting a CF mapping "named" `/foo` you can then > >> reference the mapping "by name" as simply `/foo` rather than needing to > >> write out the full path. > >> > >> > >> > >> > CF handles determining what that is when it renders > >> > it int o html. > >> > > >> > >> > >> You are 100% WRONG if you think CF does anything with mappings for any > >> purpose other than **CFML FILE SYSTEM ACCESS**. > >> > >> > >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357175 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
