I can speak only for Railo, but I assume in MX it is almost the same.
By
setting a cfoutput tag you turn on a switch for the engine to write
the
output to the response buffer and to interpret pound signs or not. It
also depends on the cfsetting enablecfoutputonly tag. So I guess it
I believe, and someone correct me if I'm wrong, that a cfml page is more
efficient if you only use cfoutput tags where they are need. The reason being
that the server doesn't have to interpret anything not wrapped in a cf tag that
it recognizes.
That being said, you also don't have to worry
The reason being that the server doesn't have to interpret anything not
wrapped in a cf tag that it recognizes.
=
People have told me that before, but if there are no pound signs in the
page I don't see how it would make much of a difference other than a
quick scan of the page for any
First question, which is better, wraping an entire .cfm file
with a CFOUTPUT, or only using the tags where you need them
in the docutment? Whichever answer, why? And finaly, other
then the fact that CF won't accept nested CFOUTPUTs with
different queries, why won't it?
First, whenever
I can speak only for Railo, but I assume in MX it is almost the same. By
setting a cfoutput tag you turn on a switch for the engine to write the
output to the response buffer and to interpret pound signs or not. It
also depends on the cfsetting enablecfoutputonly tag. So I guess it
would be a
5 matches
Mail list logo
