On Wed, 27 Oct 2004 11:51:47 +0700, stylo~ <[EMAIL PROTECTED]> wrote:
> Surely more reasonable still would be to not send anything unless I
> specifically return something, no?

I just tested this and if you have no <cfreturn> in your method and a
string return type, you should get a blank result, not a WDDX packet
(because there is no return value to encode).

> I think the cfc shouldn't care how I use the data

The CFC doesn't - you're missing the point: it's the *calling
machinery* that determines what happens to the CFC result. The CFC
always just returns data. When you make the call from a browser, what
actually happens is the CFC is called as part of the request
processing on the CF server - the CFC returns a value and the request
processing encodes it so it can append it to the HTTP response buffer.

> >You're not. If you make an HTTP request to a CFC, what comes back is
> >the HTTP response buffer *not* the returned value of the CFC. That's
> >because that's just the way HTTP works - if you request a CFM page, it
> >doesn't return a value, it writes to the HTTP response buffer.
> 
> Sorry, I don't understand why you say that.

That's why you don't understand the behavior you're seeing. I'm not
sure how to explain it more clearly. Someone help me out here??

> The cfc is specifically wrapping
> the result in XML, right?

No. The HTTP request processor is doing that. It calls the CFC. It
encodes the returned value so it can write it to the HTTP response
buffer - because that's the only thing it has to work with.
-- 
Sean A Corfield -- http://www.corfield.org/
Team Fusebox -- http://www.fusebox.org/
Got Gmail? -- I have 1 invite

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' 
in the message of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).

An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]

Reply via email to