[
Lists Home |
Date Index |
Thread Index
]
Dare Obasanjo wrote:
> I think you are overanalyzing the issue. The fact is that developers using object oriented programming languages like treating distributed applications as distributed object applications.
Yes <sigh> today's developers want everything to be objects. The list of
useful entities that are not objects is quite long - XML, relational
tables and records, higher-order functions, patterns, messages, etc. -
but developers will have none of these unless they can see them through
OOP-colored glasses, no matter how horribly awkward or inefficient the
translation.
> 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.
Thank heavens. ;-}
> Then again I have to work with a bunch of these web developer types these days so I now see their perspectives a lot better.
Bob Foster
http://xmlbuddy.com/
|
