It's Own Models: Web Services' Hand-Me-Downs

A Protocol of One’s Own

(with apologies to Virginia Woolf) Many of the clients I talk with about Web Services (WS) are concerned with security issues. This is a valid concern, not so much for simple Web Services, but certainly for more complex, higher level versions of Web Services. The entire question, however, points to a much larger fact that has emerged as I’ve explored various facets of Web Services. To date, Web Services use protocols and approaches borrowed from the World Wide Web (like HTTP, TCP/IP, SSL, etc.) These borrowed protocols work in certain situations, primarily with simple, low-level WS. The latter are generally characterized by synchronous, short-lived transactions. Higher level, more complex WS are characterized by asynchronous, long-lived transactions. Loosely coupled and usually involving intermediaries, these types of Web Services require more than these borrowed, made-to-fit protocols can provide. The important point is that every aspect of implementing Web Services will benefit from the emergence of protocols and approaches designed for the unique demands and characteristics of Web Services. These protocols are emerging, but are not yet fully established.