>>Is there any advantage or disadvantage to naming these pages with a HTM
extension rather than a CFM extension?
For the first request to the page, the difference is probabily not significant,
for any subsequent call however, the HTML page will come directly from the
client's cache, then much fa
>>that speed penalty only occurs in the firts load page right? After
that the "compiled" class file will load very fast... right?
Yes, but the same thing is true for a plain HTML file, since it will be read
from the client's cache, it will be even faster.
--
By putting the cfm extension on the end of the page, you take a performance
hit. If you're comparing it to returning a static page, the performance hit
is huge. In the grand scheme of things, it's usually insignificant.
If the site is mostly HTML with a couple of dynamic pages, then you'll
probabl
Don't think so unless you map it in the webserver. It seems to follow the
webserver root, not the CF root.
> Is it possible to use getPageContext().include() to access a file
> which isn't under the webroot?
>
> Bert
>
>
> On Thu, 2 Dec 2004 12:53:07 -0500, Michael Dinowitz
> <[EMAIL PROTECTED]>
> that speed penalty only occurs in the firts load page right? After
> that the "compiled" class file will load very fast... right?
Assuming that the page doesn't actually do anything, it won't take long to
execute. However, if all of the threads processing requests are busy, the
page won't execut
No, there's always a performance penalty for making a page go through CF
before the web server.
HTML pages always (unless specifically set up otherwise) go straight
from the hard disk to the web server to the browser.
CFM pages always (uneless misconfigured or on purpose) go from the HDD
to th
Is it possible to use getPageContext().include() to access a file
which isn't under the webroot?
Bert
On Thu, 2 Dec 2004 12:53:07 -0500, Michael Dinowitz
<[EMAIL PROTECTED]> wrote:
> CFINCLUDE will parse any page it includes, which means that it will look
> through
> the page for CF content to
CFINCLUDE will parse any page it includes, which means that it will look through
the page for CF content to evaluate. Doesn't matter if it's a plain html page or
a CF one, doesn't matter what the extension is. If you are including html
content into a CF page, it's better to use:
getPageContext().in
Dave
that speed penalty only occurs in the firts load page right? After
that the "compiled" class file will load very fast... right?
Cheers
Marco
On Thu, 2 Dec 2004 12:37:31 -0500, Dave Watts <[EMAIL PROTECTED]> wrote:
> > When developing an entire website, I occasionally develop a page with
>
There is no penalty if its htm as this wont get parsed at all by cfml
Then again I doubt there is much parsing of a page (speed hit) if
there are no cf tags
MD
On Thu, 2 Dec 2004 12:16:29 -0500, Claremont, Timothy
<[EMAIL PROTECTED]> wrote:
> When developing an entire website, I occasionally de
> Is there any advantage or disadvantage to naming these pages
> with a HTM extension rather than a CFM extension? Is there a
> speed penalty?
A .cfm file will *always* be passed to the CF engine, so even if there's
nothing for the engine to do, it's still got to break the page down etc,
so ther
> When developing an entire website, I occasionally develop a page with
> no CF-specific content whatsoever (although it happens remarkably
> rarely). Is there any advantage or disadvantage to naming these pages
> with a HTM extension rather than a CFM extension? Is there a speed
> penalty?
Ye
There's more likely a speed increase with plain HTML pages, because they
require no server-side processing before sending the content. Some
people just name all their files .cfm for continuity, others have their
static files be .html, and have to pay close attention to where their
links go.
As
13 matches
Mail list logo
