The initiative gained wide consensus among the main industry
players and the analyst ?¬?rms, with more and more important
vendors joining the ranks of the speci?¬?cation proponents and
backers as subsequent versions were released.
Software integration
needs exposed the
shortcomings of
proprietary standards
The lesson provided
by HTML was
that of minimal
requirements and
resilience
140 Hints Toward a Solution
With the problem of sheer data transfer interoperability on its
way to being solved, the market moved to consider the next
stage: advanced communication capabilities. SOAP and its associated
speci?¬?cations (see the section ???Basics??? later in the chapter)
didn??™t provide any way to secure messages from tampering
in transit, nor was there a mechanism to provide con?¬?dentiality
to communications; there were no means for a message sender
to know whether a message actually reached its destination (and
so on). Because the main purpose of web services was to connect
loosely associated parties, shortcomings such as the absence
of security were especially painful. There was still the
chance of leveraging features of the actual transport??”for
example, sending SOAP messages through HTTPS would have
guaranteed con?¬?dentiality; relying on that, however, would
have partially eliminated the bene?¬?ts of SOAP??™s platform-emancipation
efforts.
Pages:
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245