My "9 out of 10" comment was more with regard to XML -- there are occasions where the ability to have tag attributes in XML makes for a neater, more coherent interface than using JSON.
On May 30, 8:29 am, "Jonas Petersson" <[email protected]> wrote: > On 2011-05-30 15:16, DanH wrote: > > > SOAP has high-level functions that JSON doesn't (over and above the > > simple protocol level differences). Not really necessary for simple > > database queries and the like, but useful for more sophisticated > > stuff. (Disclaimer -- I've never actually used SOAP -- it's always > > been too complex for my uses.) > > > Certainly when faced with the simple choice between JSON and XML, JSON > > is the right choice 9 times out of 10. > > Well, I've used SOAP in several projects (as in "I've been given a SOAP > service someone else has built and had to conform to it") and I'm sure > there ARE real life cases where SOAP is the correct tool for the job, > but I have yet to find one. My personal estimate is that JSON is the > right choice almost 10 times out of 10 (at least when it comes to stuff > that you are likely to want to implement on a phone). Data overhead is > important to most users both when it comes to cost and time so that > pretty much disqualifies SOAP IMHO. > > Best / Jonas > > PS. My biggest gripe is that SOAP services often base64 encode > everything twice. Sure it is "binary safe", but you can easily add that > to your tailored JSON data too. YMMV. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
