Sreenivasa,
I'll let others respond to the performance questions, but I'm happy to tell
you about UDDI.
UDDI is a static registry of businesses and services, not an object request
broker. You use UDDI to find a business that offers the kind of service you
want, and then to find information on how to make use of that service --
such as a description of the web service interface (such as a WSDL file),
the access point used to invoke the service (a URL), and any other
information that you might need to negotiate a contract with the service
provider (contact information, terms and conditions, quality of service
requirements, etc.).
You use UDDI to find the information that you need to build an interface to
talk to a web service. Although some might argue that you can use UDDI to
dynamically connect to services at runtime, for most practical purposes,
UDDI is a design-time discovery service. UDDI does not return a client
proxy -- you have to construct your client proxy from the information you
retrieve from UDDI.
There is a public UDDI registry called the UDDI Business Registry (UBR). The
UBR is currently hosted by IBM and Microsoft. Each company hosts a complete
replica of the registry, so it doesn't matter which one you access. You can
find lots of information about UDDI, including the programmers reference, at
www.uddi.org.
You can play with UDDI by going to either the IBM or Microsoft UDDI web
pages:
http://www-3.ibm.com/services/uddi/
http://uddi.microsoft.com
You can also interface with the UBR nodes programmatically using SOAP
messages. Query the UBR registry and search for IBM or Microsoft and find
the service descriptions for their UDDI Business Registry services. (note:
the UBR is a web service)
You can also set up a private UDDI registry to experiment with. I know of
four different UDDI server implementations (all are free at the moment):
- http://www.alphaworks.ibm.com/tech/webservicestoolkit
- http://www.idoox.com/products/wasp_uddi/download/index.html
- http://www.themindelectric.com/products/download/download.html
- http://sourceforge.net/projects/uddi/ (see also www.juddi.org)
The juddi.org project is open source (BSD-style license)
You also might want to join the UDDI discussion lists, hosted by Yahoo
Groups. See http://groups.yahoo.com. The UDDI groups are:
- uddi-general
- uddi-technical
Regards,
Anne Thomas Manes
Sun Microsystems
-----Original Message-----
From: P Sreenivasa Rao [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12, 2001 4:22 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: performance issues in Web Services
Hi all,
I have some doubts regarding the performance issues(u can call them as
disadvntages ) of Web Services.
Actually,we'll depend on the performnace of Service Provider in web
services.So in the internet scenario,the performance will be a bottleneck as
it'll take much time (due to more no of hops or more traffic to SP etc) to
get response.
Another thing, I dont know the necessity of request broker in the web
serives scenario.Is it replaced by UDDI registry or UDDI registry is the
implementation of request broker?Is there any public UDDI registry
available? I tried with IBM's site but I dint get the actaul link pointed in
their documentation.
Finally,what are the other advantages and bottlenecks in this Web serivces
scenario.
Thanks a lot for one and all.
Awaiting your early response.
Thanks and regards,
Sreenivas,CMCLtd
