So you're saying JSON is not an object, it's a string? What does the O
stand for then? The OP gave this example JSON:
{
"product_id":"000003",
"product_name":"Sample shoe",
"product_brand":"Shoe Brand",
"product_slug":"slug3",
"product_description":"description3",
"product_active":"1",
"product_type":"shoe",
"product_gender":"youth",
"product_sizes":"14",
"product_style":"style 3",
"product_categories":"3",
"product_shipping":"shipping 3",
"product_cost":"40.0",
"product_retail":"70.0"
}
In an ajax response with the reponse type as 'json' (or text and
eval'd yourself if you like), that's an object. It's composed of
name:value pairs. The names are strings. If you don't like what the
RFC says, take it up with Douglas Crockford.
On Apr 16, 2:25 pm, dhtml <dhtmlkitc...@gmail.com> wrote:
> On Apr 16, 12:42 am, mkmanning <michaell...@gmail.com> wrote:
>
> > Just an FYI, but there's no 'object side' of the json in your example.
> > It just an object, consisting of name-value pairs. While you can leave
>
> No, it is not an object. It is a string.
>
> > quotes off of the names, they are strings which, according to the RFC,
> > should be quoted. Doing so will not cause problems, and will save you
> > from potentially running into a situation where your name conflicts
> > with one of the excessive number of reserved words.
>
> > On Apr 15, 7:05 pm, sneaks <deroacheee...@gmail.com> wrote:
>
> > > the way i see it, there are quotes on the object side of the json
> > > where there should be no quotes...
>
> That makes about as much sense as something the OP would post.
>
> Garrett
