Correct. So, the example posted has to be corrected to either numbers or strings, but the single quotes have to go.
On Tue, Sep 2, 2014 at 10:59 AM, Lonnie Olson <[email protected]> wrote: > On Tue, Sep 2, 2014 at 9:42 AM, Skylar Walker <[email protected]> > wrote: > > If the JSON string you posted is the exact one you are receiving, you > will > > have the most trouble with the fact that it's invalid JSON. JSON requires > > double quotes on strings, so you would expect the following: > > > > { > > "timestamp": "139396594", > > "acct1": > > { > > "available" : "12594.56", > > "pending" : "415.4264" > > }, > > "reserve" : > > { > > "available" : "175.11" > > } > > } > > Correction, JSON does *not* require double quotes around numbers. > > It can be wrapped in quotes, but that means it will be decoded as a > string, which may be a critical difference depending on the decoder > tool and/or language used. > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
