JSON has several limitations as it doesn't usually send Strings by reference, it doesn't usually send Object traits (i.e. property names) by reference, and it doesn't usually support strongly typed class information (although I've seen unofficial suggestions as to how this could be achieved in JSON).
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Marvin Froeder Sent: Wednesday, May 30, 2007 10:39 AM To: [email protected] Subject: Re: [flexcoders] Re: Object serialisation + SimpleXMLEncoder Yes, I had try... Just can't believe the JSon results... This can not be right... or worse can be =( VELO On 5/30/07, Jerome Clarke <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: you might find this useful benchmark - http://www.jamesward.org/census/ <http://www.jamesward.org/census/> On 5/30/07, Marvin Froeder <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Well... I had make the serialization works... Didnt trye deserialization.... lets see this URL before.... Another question... I had see something about the Flex+Json performance problem.... is that true? Was told me the parse from Json-XML to AS3 objects is too slow. Is that true? VELO On 5/30/07, brent_trx < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Sorry for the double-post ... I actually have an example of this up online, if anyone wants to check it out. I use Darron Schall's ObjectTranslator to assist with strong-typing of deserialized responses. I've since adopted it to JSON which is handling pretty pimptasticly. http://booleanbetrayal.com/2007/05/18/httpservice-xmldecode-objecttransl ator-and-rabidsquirrels/ <http://booleanbetrayal.com/2007/05/18/httpservice-xmldecode-objecttrans lator-and-rabidsquirrels/>
