Over in xml-dev, in a discussion on why JSON is gaining ground, Dare Obasanjo writes:
Amen!The fact is that developers using object oriented programming languages like treating distributed applications as distributed object applications. This is the primary reason for all the interop woes with regards to SOAP/XSD/WSDL.
With AJAX, there isn't really the option to go down the SOAP/XSD/WSDL road because no web browser has a WS-* built into its Javascript object models and I doubt we'll see one anytime soon. So that leaves parsing XML by hand when it is received from the server and parsing into objects on the client or picking a different format that is easier to parse into objects. Web developers are very practical which is why I'm not surprised to see that XML isn't always the first choice in this scenario.
no web browser has a WS-* built into its Javascript object models
Having never used it (I am not a fan of SOAP really), I can't say how thorough and useable is Mozilla's support, but it does seem to provide support for using SOAP in Javascript, eliminating the need for messing with XML.
Re:Web Services support in browsers
ziggy on 2005-08-26T16:22:48
Hm. Hadn't seen that. Dare works at Microsoft, so when he says No web browser..., you're free to read that as Neither IE nor Safari...;-)
