[LEARNING bLOG] | [Freelance Web Designer] | [and "Rohan" is part of my surname]
marlajee Borstone wrote:But unfortunately I don't have any idea if JSON.
[LEARNING bLOG] | [Freelance Web Designer] | [and "Rohan" is part of my surname]
Isn’t the “JSON vs XML” debate a bit like a “PNG vs JPG” debate, in which developers of image-display applications decide their apps will handle one or the other?
In a services-oriented world, once you’re past same-site restrictions (via signed scripts or trusted zones), you will have occasion to consume services providing SOAP, POX and JSON data, based on the service-providers preference regardless of your’s. Sure, if you control the service side, JSON can be much more efficient; but existing Web services won’t add this to their APIs just to make your life easier.
IMHO, the smart path is implementing a framework that can handle various data formats, via various retrieval methods (SOAP, REST, HTTP-POST, etc.) — possibly marshalling everything to JSON for faster processing.
[LEARNING bLOG] | [Freelance Web Designer] | [and "Rohan" is part of my surname]
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |