There are a few reasons this could / would be done.
1)anyone remember .dbm files ? Oh yeah, their CF file look at your
mappings ...their run through the same CF Stub as CFM files thanks to
this mapping ability.
2) A bit of obfuscation..... on the client end it is more difficult to
tell what you are running on the server with generic HTM file
extensions. Yeah, yeah CFID and CFTOKEN are set ...but you could
concoct some elaborate scheme to still have home-grown session
management and not use CFID and CFTOKEN.
3) Common name space. What's one of the biggest problems on site ?
Broken links. Reducing the options for file extensions reduces the
possible errors. Ever built a link to a someFile.cfm ...only to
remember later it was a static HTM file.
4) Integration with the old....supposed you have a big honking flat site
that uses all htm files ... you now want to replace a few key files on
the site with CF files (for example customer service numbers) ..... can
you justify the cost to go back and fix 10,000 referring links to this
single CFM page ? why not just have CF process all the HTM files and
replace the offending files in this beast of a site.
5) Its a web server thing : these types of mappings (whatever
incarnation they appear in on the web server of your choice) are how web
servers know when / how to dish off certain files for processing. The
web servers prerogative to have certain types of files processed by a
given program.
Like I said, "could/would" not *should* ....its just one of those
abilities sort of like wiggling your ears. You could and you might.
-eric
------------------------------------------------
Common sense is genius dressed in its working clothes.
-- Ralph Waldo Emerson
Eric Barr
Zeff Design
(p) 212.714.6390
(f) 212.580.7181
-----Original Message-----
From: Tony Schreiber [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 28, 2001 6:48 PM
To: CF-Talk
Subject: Re: Mapping to an extension PART TWO
To hide the fact you're using CF?
> what i meant was, whats the point of mapping to an extension? why use
htm
> instead of CFM? thats what i mean
>
> -----Original Message-----
> From: Philip Arnold - ASP [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 28, 2001 4:00 PM
> To: CF-Talk
> Subject: RE: Mapping to an extension
>
>
> > why would anyone wanna do that?!!
>
> Some sites send .htm and .html to either CF or something else - it is
a
> performance hit on non-dynamic pages, but it covers up a little of
what you
> use
>
> Doing it to an extension of more than 3 or 4 characters would be just
> idiotic and more of a pain than anything
>
> Philip Arnold
> Director
> Certified ColdFusion Developer
> ASP Multimedia Limited
> T: +44 (0)20 8680 1133
>
> "Websites for the real world"
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> **********************************************************************
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
