[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> -----Original Message-----
> From: Dare Obasanjo [mailto:dareo@microsoft.com]
> Sent: 23 April 2002 06:14
> To: Bill de hÓra; Dave Winer; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] What does SOAP really add?
>
>
> You realize your post says nothing, right?
Far from it.
> When asked "what are the technical advantages of using SOAP",
> responding with "it doesn't handle some tough problems, so
> what?" does not prove any point.
Ignoring a question I wasn't asked for now, I read Sam Ruby's
article as largely about data typing, not about SOAP. I'm not
intending to slight the man, and I'm something of a fan of Axis and
what it's trying to achieve as a performant software design. I
think the article makes one mistake in that it confuses corner
cases with orthogonality. As for what does and does not work in
SOAP, I think he's right. SOAP may bring these problems into sharp
focus, but they are not, in my humble but correct opinion, SOAP
problems. It's before my time, but I understand the database world
have had similar problems in the past with dates and possibly truth
values. I don't believe any kerfuffle about floating point numbers
to be a new problem. They're all somewhat more general than that,
and should be treated independently of the carrier protocol. Mixing
the two up doesn't help. If we come to the conclusion that a
carrier protocol isn't worth much without standardized types,
that's fine. At least we move the interoperability question closer
to the software abstractions. and away from machine architecture.
Bill de hÓra
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBPMUr7OaWiFwg2CH4EQJYmQCfTJNLTVrq3Xcu3IQQwqYzxJNykLoAoJnB
F1p+BDNMa0mQSfpvphiBJlhu
=vF6Z
-----END PGP SIGNATURE-----
|
