Sam,
Nice article!
The issue of complying with other standards (in respect of trailing zeros)
reminds me of the kind of problems that CORBA interoperation gets into.
It's not too hard to get interoperation at the level of IIOP, but when you
add security (CSIv2 etc.), transactions (OTS), and interactions between the
ORB and naming services, the probability of satisfactory interoperation
rapidly decreases.
We need to be aware of this as security and other standards that build
othogonally on SOAP emerge. If there is a proliferation of such standards,
it may be necessary to define common 'stacks' of standards that will be
subject to interoperation testing together.
Glyn
Sam
Ruby/Raleigh/I To: [EMAIL PROTECTED]
BM@IBMUS cc: [EMAIL PROTECTED]
Subject: Quest for SOAP Interoperability
01/02/02 15:18
Please respond
to axis-dev
It is my belief that in addition to the SOAP standard, we need to document
a set of best practices and a create classification of errors that identify
potential interoperability issues. I jotted down some of my thoughts on
the subject and posted them at:
http://radio.weblogs.com/0101679/stories/2002/02/01/toInfinityAndBeyondTheQuestForSoapInteroperability.html
What do people think?
- Sam Ruby
