>Seriously tho... if you're using AJAX but not using XML, what's to >differentiate that from simply using JS? (Asside from the buzz-word >appeal.)
I was actually rather (pleasantly) surprised that i didn't have to encode my response in an xml syntax in order to use it, but only because my needs were *extremely* trivial and using the very minimum legal xml would have doubled the size of my data packet. If i needed to return structured data (say i wanted to populate a drop down or somesuch) then i'd certainly turn to XML rather than start messing about with some form of delimited lists or other "roll your own" methods. Using SOAP based web services via js has two main issues: encoding a valid SOAP request and parsing out the SOAP response. For the first, as Barney pointed out, you rarely need to - every classic web app out there is a testament to what you can do with post/get. As for client side xml handling, you could do quite a bit with WDDX (which probably works in more browsers than XMLHttpRequest, but that's kinda beside the point). It's a "bang for your buck" kind of argument (and i'll freely admit that my attitudes to cross browser scripting were formed back in '98 ;) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:214230 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
