On Wed, Sep 10, 2008 at 7:10 AM, Reinier Zwitserloot <[EMAIL PROTECTED]>wrote:
> Here's an alternative idea: Let the new API exist only for reading - I > never really had an issue with the existing API's utility when > creating JSON - just when reading it. Solves all these problems. If > that's fine, then it's ready to go right now, pending an addition to > the regexp that finds string literals during the validation step as > per Scott Blum's comments. > By the way, that was merely what I thought of off the top of my head. I kinda feel like this proposal should circulate to a much broader audience even than GWTC, where some experts in secure JSON parsing could weigh in, before I'd be comfortable advertising it as a "safe" parse. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
