Opening a web service in WCF: Ws-Discovery or UDDI?

Question

I know the difference between UDDI and Ws-Discovery (I know a good place to find a service and broadcast). But my question is: what is the easiest way to open a web service in WCF? Most simply, I mean what is already implemented in WCF and can be used now? I have not seen the built-in WCF implementation for UDDI or Ws-Discovery.

Do you have any link or experience sharing these two protocols in WCF?

UPDATE

Now I am thinking of three solutions awaiting WS discovery on .NET 4.0, or perhaps creating their discovery binding with the Peer to Peer binding provided by WCF. This way I can broadcast the request. Or using the implementation provided by the reference eed3si9n.

I think I will make a gateway interface to easily change the latter.

Answer 1

.NET 4.0 will have WS-Discovery. See Messaging Improvements in .NET 4.0: (Part I Discover) Using WS-Discovery in WCF 4.0 . Claudio Masieri, meanwhile, provided the implementation. See WS-Discovery for WCF .

A regular implementation similar to UDDI is also implemented. See Discovery of Windows Communication Services .

Imagine you have 200 customers using your Wcf funk service. They all have a section like this in their conf file:

<client> <endpoint configurationName="default" address="http://localhost/servicemodelsamples/service.svc" binding="wsHttpBinding" bindingConfiguration="Binding1" contract="IDataContractCalculator" /> </client> <bindings> <wsHttpBinding> <binding configurationName="Binding1" /> </wsHttpBinding> </bindings> 

Now you have decided to change the existing endpoint (server side) with a new one that uses SSL for security reasons. How do you update your customers? You can quickly see that he can become tedious. So, the idea that I want to tell in detail here is to implement the discovery of a service similar to what UDDI does using a metadata recognition tool to get configurations from a service to create a dynamic proxy server allowing the client to discuss with the service.

This person has the same problem as yours and seems to have a working solution.

Answer 2

UDDI provides a central registry for storing information about available Services. It supplies a directory where consumers can find the services that suit their needs. This directory information directory phone allows consumers to find services by name, address, contract, category or other data. UDDI is possible as a DNS web service.

On the other hand, WS-Discovery provides a protocol for discovering services that come and go from the network. When a service joins the network, he informs his peers of his arrival by broadcasting a greeting message; Similarly, when services are down from the network they are multicasting a bye message. WS-Discovery does not rely on a single node to host information on all available services such as UDDI does. Rather, each node forward information on available services in a special order. This reduces the amount of network infrastructure needed to open services and makes loading easier.

Quote from: http://travisspencer.com/blog/2007/09/post.html

Here is a good list of properties: http://laflour.spaces.live.com/Blog/cns!7575E2FFC19135B4!728.entry

Answer 3

jUDDI has a .NET client that you can use. This greatly simplifies working with UDDI.

From experience, there are only two or three functional implementations of WS-Discovery.

• Apache CXF, but only when run outside the container
• This one: https://code.google.com/p/java-ws-discovery/ , which does not work in Jboss and is not supported
• Microsoft .NET 4.0ish

UDDI you can access everything. There are many client and server implementations. (Only versions 3 are listed here)

• IBM WS-Registry
• Apache jUDDI
• Microsoft UDDI v3 with Biztalk (free with server 2008)
• HP SOA / Systinet or whatever he calls now
• Wso2 has something
• ebXML has some kind of bridge or adapter

There's even a REST endpoint for UDDI3 (jUDDI 3.2 has this, XML or JSON responses), which opens it up to many other possibilities.

In addition, the data that can be combined with WS-Discovery is somewhat limited compared to the almost unlimited data that you can connect to UDDI.

This is just my 2 cents.