3 ms·
It has to do with the awful XML generated by automatic tooling (SOAP by WCF and JEE). Hand-generated XML can be just as nice as using hand-generated JSON, and
by _pmf_ 13y ago
It has to do with the awful XML generated by automatic tooling (SOAP by WCF and JEE).
Hand-generated XML can be just as nice as using hand-generated JSON, and on the other hand automatic domain-model-to-JSON mapping can be as ugly as any XML monstrosity.
- peterwwillis 13y agoThough for the same dataset, XML will be slower to parse. For performance's sake use JSON.
- arethuza 13y agoI suspect that depends a lot on what platforms are used at the client and server.
- _pmf_ 13y ago> Though for the same dataset, XML will be slower to parse. For performance's sake use JSON. Loading a huge JSON file is almost certainly slower than using a SAX parser for a huge XML file. Maybe there are SAX like approaches for JSON, too.
- icebraining 13y agoYes, it's called "streaming". Like in XML, you can also used a mixed approach. See e.g. https://sites.google.com/site/gson/streaming https://sites.google.com/site/gson/streaming
- veesahni 13y agoMost languages have the concept of arrays and hashes, which map unambiguously & idiomatically to JSON via generic serializers. Creating idiomatic XML, on the other hand, is a little more tricky. Should something be a tag or an attribute? What should it be named?