the HTML stream, but rather it's stopping output from happening at all
(regardless if you'll catch the output before it hits the stream with your
application code).
I haven't checked a compiled template, but I'd imagine every time out output
something (static or dynamic), it ends up in a construct something like
this:
if (! request.isOutputSuppressed)
out.write("my content");
In other words, before your compiled CF template will output anything, it'll
check to see if output is being suppressed, and if so, skip the outputting.
To get the behaviour you think is more intuitive, CF would have to output
everything, but somehow mark the sections that are within CFSETTING tags,
and then after your code is done generating the request, process the
generated content, and trim out all the bits that were marked as "to be
ignored".
Cheers,
barneyb
> -----Original Message-----
> From: Dave Carabetta [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 19, 2004 2:14 PM
> To: CF-Talk
> Subject: Re: cfset vs. cfsavecontent
>
> On Mon, 19 Jul 2004 14:02:33 -0700, Barney Boisvert
> <[EMAIL PROTECTED]> wrote:
> > You have output disabled with CFSETTING? If so, you'll
> need to wrap the
> > CFSAVECONTENT in a CFOUTPUT if you want the text to display.
> >
> > Cheers,
> > barneyb
> >
>
> Thanks Barney, that was it. Out of curiosity, isn't that a bit
> counter-intuitive? I mean, the whole purpose (in this case, at least)
> is to write the contents to a variable to pass back from my CFC. If
> I'm not writing anything to the output stream in cfsavecontent call
> itself, why do I need the cfoutputs? Just curious.
>
> Thanks again.
>
> Regards,
> Dave.
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
