× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Maurice O'Prey wrote:
Would it be too much to ask for a description of a 'real world'
implementation of JSON, one where XML and web services would not fit nor
perform very well?

I don't doubt the usefulness of JSON, I just need to learn by example (and
learn to live within standards)

Maurice O'Prey
Did you see my initial post?

JSON:

[ "customerid" : 1123454, "name" : "Joe Pluta", "email" : "junkmail@xxxxxxxxxxxxxxxxx" ]


*By itself*, the *raw* XML is nearly the same:

<customer customerid = 1123454 name = "Joe Pluta" email="junkmail@xxxxxxxxxxxxxxxxx" />


But this assumes that you use attributes rather than children. Many people don't and children fatten XML considerably:

<customer>
<customerid>1123454</customerid>
<name>Joe Pluta</name>
<email>junkmail@xxxxxxxxxxxxxxxxx</email>
</customer>


That's almost a 50% increase, I think. But then go to a standard web service using SOAP, and you're talking about typically at least 300 characters of SOAP envelope, which would more than quadruple the size of the original message.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.