It depends on how much information you
need out of the data you received. If you plan on doing a lot of reading and
manipulating of the data then having an xmlDecoder and creating value objects
is probably worth it. If you can use the XML directly (or the default decoding)
then I’d probably stick with the simple decoding (or resultFormat=”xml”).
If you’re not going to send the data back to the server then there’s
no need for an xmlEncoder at all.
Matt
> my decoder could just as easily build the XML document as a
> string.
You mean a XML string or XML to name-value
pairs...
If you want to convert a XML object to string, you
can do _xml.toString(),
it would give you entire xml structure as
string...
Does your encoder do same?
-abdul
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Friday, April 15, 2005 6:17 PM
To: [email protected]
Subject: [flexcoders] HTTPService xmlEncoder
Hi,
I have a HTTPService for which I have written a
xmlDecoder to build my
VOs from data received from my service. I am
not about to send data
to the service, and was wondering if using the
xmlEncoder was an
overkill - my decoder could just as easily build
the XML document as a
string.
What are the pro's and cons of each ?
Thanks.
Yahoo! Groups Links
Yahoo! Groups Links
|
