> I understand that JSON is a “string representation of an object” and not > literally an object. Nonetheless, I think you would agree that it can be > useful to have routines that simplify looking up the values that are stored > in those strings.
Actually, I wouldn't agree. Why should there be a whole set of JSON routines that duplicate existing syntax and functionality in collections (Active4D) or objects (4D)? I'm trying to explain that JSON is not meant to be used in that way. JSON is meant to be used like this: - receive JSON data - convert to object - access and manipulate data in the object or - set data in an object - convert to JSON - send JSON data That's how it's meant to be used, at a single point just after receiving or just before sending. As I said before, there is no point in looking up one or two values in a JSON string before parsing it in its entirety, because an implementation of that functionality would have to be parse it in its entirety to lookup those values. Peace, - Aparajita _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
