Matt, We tried to convert the XMLObjectOutput (even with the help of MM support) and we still ended up with something that was only about 97% compatible. You can always find cases of XML that it does not give the same results for.
The danger is that if you guys change the internals of how HTTPService does the deserialization, the our code will be old and out of sync. I think it would be good if this code can be called externally (then we do not have to see your gnarly code!). Make it a public function. Thanks Jonathan On 5/3/05, Matt Chotin <[EMAIL PROTECTED]> wrote: > > > > I do J It's pretty gnarly so we haven't exposed it. What are you trying to > do? The XMLObjectOutput class in the extras does a pretty decent > deserialization job. You could adjust that as appropriate to suit your > needs I'm guessing. > > > > Matt > > > > ________________________________ > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Todd Matthews > Sent: Tuesday, May 03, 2005 4:58 AM > To: [email protected] > Subject: [flexcoders] XMLDecoder class > > > > > Does anyone have the actual source for XMLEncode/XMLDecode method that > the HTTPService implements? > > > > > > ________________________________ > 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 the Yahoo! Terms of Service. 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/
