On Mon, 25 Oct 2004 16:06:52 +1300, Adam Cameron <[EMAIL PROTECTED]> wrote:
> When I have a method return a string... It returns a string.  It does
> not return a string wrapped in WDDX baggage.  So that's not consistent.

If you call a CFC method from a browser, it always returns the result
the same way: as an XML string which the browser can display. If you
call a CFC method as a web service, it always returns the result the
same way: as a SOAP value. If you call a CFC method from Flash
Remoting, it always returns the result the same way: as a
binary-encoded representation of the ActionScript format data. If you
call a CFC method from another local CFC or a web page, it always
returns the result the same way: as a CF value. It couldn't be more
consistent than that - it returns data in a format consistent with the
calling mechanism.

> Well... Because I have all the "output" that I actually require in the
> return value from the function

If you call a CFC method from a browser and expect to get output,
you'd better say output="yes" and write the output to the buffer -
just like you would for a CFM page. Or have a displayXxx() method that
calls xxx() and outputs the result.

> DO YOU actually think it's *sensible* for a string return value to be
> wrapped in WDDX when you invoke it via HTTP?

Yeah, makes perfect sense to me - even before I read the docs.

I think CF is being very consistent - I think you're the one asking
for inconsistent behavior.
-- 
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