谁关心UDDI?

原创 2002年04月30日 09:12:00

Who Cares About UDDI?

David Chappell -
April 25 , 2002

 

Web services are the most important thing happening in distributed computing today. And since distributed computing has become the norm, that puts them high on the list of important things, period. As usually described, the trinity of Web services technologies includes SOAP for invoking remote operations, WSDL for specifying what those operations look like, and UDDI for . . . well, what, exactly? What is UDDI actually good for?

 

Theoretically, UDDI stores information that helps clients select and use a web service. This might mean information about the kind of service provided, who provides it, and potentially even how much it costs. UDDI is a very open-ended technology, and so it can store all kinds of data. Pragmatically, however, the main thing required to access a Web service is its WSDL definition. Tools such as Microsoft’s Visual Studio.NET and IBM’s WebSphere Studio can read a WSDL file and generate the client proxy required to invoke the operations described in that file. While there are UDDI servers available on the Internet today, there’s not much in them. In particular, they don’t contain many WSDL files.

 

This isn’t really too surprising. After all, the primary application of Web services today is enterprise application integration (EAI). Connecting existing code is a pressing business problem, one solved quite effectively by Web services, and staying inside the firewall lessens the challenging authentication and privacy issues that can accompany SOAP today. For both of these reasons, EAI has proven to be the killer app for Web services. Yet EAI interconnections are quite static, and they don’t generally require Internet access. Accordingly, today’s Internet-based UDDI servers are largely irrelevant to the problem. There are simpler ways to discover the WSDL interface of the desired Web services, such as having it sent to you via email by your fellow developer on the project.

 

The next most important category of Web services applications today is probably business-to-business, or B2B, integration across the Internet. Internet-based UDDI servers could potentially be more useful here. Once again, though, today’s B2B interactions are generally quite static–business partners agree in advance to communicate–so there’s no need for the very general service that UDDI can provide.

 

So when would UDDI be useful? One possibility is applications running in a world of widely available Internet-based Web services, with searches and frequently changing connections the norm. Here, UDDI’s very general capabilities to describe what’s available and to provide the information needed to choose and communicate with the appropriate service might be useful. But don’t hold your breath waiting for this world to arrive: it won’t be here anytime soon. Dynamically discovered Web services face a host of problems, including security, market demand, and charging mechanisms. While some Web visionaries tout the inevitability of this world, I confess to some skepticism. It may never arrive.

 

UDDI might also be useful as an intranet-based service, one that could be used to learn about locally available services. This is a more plausible alternative, but still not one for which any substantial need exists today. Intranet-based projects typically don’t change that often, and so a specialized directory service is probably more trouble than it’s worth.

 

Given UDDI’s problems, it’s fortunate that a more recent specification produced jointly by Microsoft and IBM provides a simpler, cleaner answer to the core problem of finding WSDL definitions. Called WS-Inspection, it defines a straightforward XML document structure for finding either a WSDL file for a particular Web service or its UDDI description. While WS-Inspection isn’t yet widely supported, it looks likely to become an important part of the Web services technology arsenal. And while UDDI may one day be a useful standard, it has so far remained the least important of the big three Web services technologies.

web服务器:SOAP,WSDL,UDDI

一、web服务简介     Web Services是一个可以将应用程序变为Web应用程序,将自己本地的应用程序信息通过网络,发布到网络中,让别人通过浏览器访问本地信息。     Web Serv...
  • liutengteng130
  • liutengteng130
  • 2013年06月26日 20:46
  • 3538

职场英语:同事生病表示关心的英语句子

职场英语:同事生病表示关心的英语句子 如果发现同事身体不舒服,或者大病初愈刚刚回到工作岗位,就一定要对别人表示关心,并提示他请假看医生或者好好休息。     You look a little ...
  • waj89757
  • waj89757
  • 2013年03月27日 09:41
  • 2582

一个男人关心的东西决定了他的层次

有些时候当我感觉有些消极的时候,我会需要一些东西去刺激我,让我走出困扰,重新振作起来,就是这些励志的东西,当然,这些东西是给我一个思考的空间,它们只是一些参考意见。最近我在考虑的问题是,我绝对不能把鸡...
  • loveRooney
  • loveRooney
  • 2015年01月29日 16:23
  • 871

如何理解Linus Torvalds的“什么才是优秀程序员”的话

Linux的创始人Torvalds在一次演讲中有一段涉及“什么才是优秀程序员”的话: “烂程序员关心的是代码。好程序员关心的是数据结构和它们之间的关系。” 这句话听起来很直白,但未必所有人...
  • yafei450225664
  • yafei450225664
  • 2013年04月25日 18:59
  • 668

SOAP,WSDL,UDDI之间的关系

SOAP(Simple Object Access Protocol) 简单对象访问协议; WSDL(Web Services Description Language) Web服务描述语言; UDD...
  • CHS007chs
  • CHS007chs
  • 2016年07月13日 09:45
  • 189

蓝桥杯vip练习 Huffman树

问题描述   Huffman树在编码中有着广泛的应用。在这里,我们只关心Huffman树的构造过程。   给出一列数{pi}={p0, p1, …, pn-1},用这列数构造Huffman树的过程...
  • u010057965
  • u010057965
  • 2014年04月16日 19:23
  • 1257

那些过分的关心,其实不是关心

生活中很多人都会有这样一种体验。   即当我们对某个人表现出过分的关心,或者对其某种行为表现出过度关注的时候,非但不会获得对方的感激,反而会遭到对方莫名其妙的冷处理,甚至抗拒与反感。 ...
  • bozai2
  • bozai2
  • 2017年01月20日 14:38
  • 964

Serverless架构设计指南,你关心的都在这里

原文:The Comprehensive Guide to Serverless Architecture 作者:Jignesh Solanki 翻译:雁惊寒 摘要:本文详细介绍了无服务器...
  • dev_csdn
  • dev_csdn
  • 2017年12月30日 04:42
  • 3943

SOAP、WSDL、UDDI详述

http://zero696295.iteye.com/blog/1555092 SOAP(Simple Object Access Protocol) 简单对象访问协议; WSDL(Web Se...
  • czplplp_900725
  • czplplp_900725
  • 2013年03月13日 10:59
  • 790

如何关心女朋友?

本文大部分来自于 知乎上的 如何关心女朋友? 用韩寒微博上的一句话:其实我一直觉得所谓爱,就是陪伴,没太多别的。 1.回到家,先别做其他的事,先找她,拥抱她。 2.问她这...
  • dlf123321
  • dlf123321
  • 2016年04月06日 22:43
  • 809
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:谁关心UDDI?
举报原因:
原因补充:

(最多只允许输入30个字)