If you know that your JSON is "wellformed JSON" (and not just the more liberal JavaScript's literal object notation), then use parseStrict. Only use parseLenient if you know your "JSON" isn't actually JSON (i.e. from a "legacy" server). That should be the rule IMO, independently from performance.
It also turns out this is the fastest, except in IE6/IE7 and "older Safari" (JSON.parse was added in Safari 4.0.3 IIRC; I don't know for Mobile Safari but I guess there are still some iPhones out there without JSON.parse support). Most other "older browsers" without JSON.parse are probably gone from the Internet now (Firefox 3.0, Opera 9) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
