I have a set of VO's in the application that need to be sent to the server as XML. I was debating whether I should provide the objects and specify an xmlEncoder to the HTTP Service, or simply do the encoding use Strings as the request arguments to send.
At this this time, I have decided to go ahead and specify an xmlEncoder. Thanks. --- In flexcoders@yahoogroups.com, Abdul Qabiz <[EMAIL PROTECTED]> wrote: > > 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: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] > Sent: Friday, April 15, 2005 6:17 PM > To: flexcoders@yahoogroups.com > 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 <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
