Addressing Web Services Interactions

 
 
By Peter Coffee  |  Posted 2004-08-16 Email Print this article Print
 
 
 
 
 
 
 

Vendor agreement on WS-Addressing spec paves way for richer interaction and improved efficiency.

I remember a poster in a college dorm room, back in the previous century, that said "I finally got it all together, but then I forgot where I put it." Information systems have historically been good at putting things together, and in their latest Web services incarnations theyve even gotten good at making things appear to be together without the burden of actually moving them around; until recently, though, IT systems have also made it difficult to figure out where things could be found. Perhaps were turning a corner with developments such as the WS-Addressing specification that was put forward last week by a team of authors from Microsoft, IBM, Sun Microsystems, BEA and SAP.

At first glance, its easy to dismiss WS-Addressing as merely a new formalism for something that people had already figured out how to do with extensions to URLs. As IBMs Doug Davis observes, one can always identify an instance of a Web service by appending something such as "?resourceID=123" to a URL, or by adding a SOAP header such as "<widget:resourceID>123
</widget:resourceID>."

The endpoint references defined by WS-Addressing enable something more, though, because they provide a means of passing around references to Web services locations independent of the transport mechanism; the resulting conversations arent limited to a two-way exchange between a request point and a service point. Avanade Engineerings Steve Maine points out the implications, for example, for much more efficient implementations of multi-instance services with queues for handling requests and responses.

The Middleware Companys Steve Wilkes offers a more fully developed description of the opportunities to write "composite applications," saying: "Partner endpoints can be dynamically configured; all parties taking part in a process know how to relate messages to a particular process instance and each other."

Steve Eichert adds to Maines comments, saying, "Instead of limiting ourselves by always having our message response returned to the place that it was invoked from, we can introduce all kinds of flexibility regarding how the response is handled. We have the ability to chain web services together, and provide a dynamic pipeline for processing our message. WS-Addressing is cool."

Wilkes comments get an ironic seasoning from the fact that his former employer, AltoWeb, closed its doors just a little more than a year ago: Analysts at the time pointed to that closure as a sign of the consolidation that they felt was bound to take place in Web services vendors ranks. With major players such as IBM, Sun, Microsoft, BEA and Oracle offering complete software stacks, observers such as John Meyer of Forrester Research suggested that "Companies like M7, Bowstreet and others are going to have a hard time surviving in the future, especially when the other vendors have an entire stack to offer."

I hope that vendor-neutral, royalty-free mechanisms like WS-Addressing will make Meyer wrong about the loss of opportunity for smaller providers. With 75 percent of enterprises now estimated to be actively deploying Web services, buyers will be looking for vendors with domain expertise to give them an edge over those who merely purchase and deploy commodity technologies. With wireless and automotive platforms moving IT out into the real world, and not merely navigating around its own imaginary world, its important that IT providers with specialized experience be able to interface reliably with standards-based platforms.

Tell me what youll do when you know where your services are at peter_coffee@ziffdavis.com. To read more Peter Coffee, subscribe to eWEEK magazine. Check out eWEEK.coms Developer & Web Services Center at http://developer.eweek.com for the latest news, reviews and analysis in programming environments and developer tools.

Be sure to add our eWEEK.com developer and Web services news feed to your RSS newsreader or My Yahoo page

 
 
 
 
Peter Coffee is Director of Platform Research at salesforce.com, where he serves as a liaison with the developer community to define the opportunity and clarify developers' technical requirements on the company's evolving Apex Platform. Peter previously spent 18 years with eWEEK (formerly PC Week), the national news magazine of enterprise technology practice, where he reviewed software development tools and methods and wrote regular columns on emerging technologies and professional community issues.Before he began writing full-time in 1989, Peter spent eleven years in technical and management positions at Exxon and The Aerospace Corporation, including management of the latter company's first desktop computing planning team and applied research in applications of artificial intelligence techniques. He holds an engineering degree from MIT and an MBA from Pepperdine University, he has held teaching appointments in computer science, business analytics and information systems management at Pepperdine, UCLA, and Chapman College.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date
Rocket Fuel