Browse by Tags
All Tags »
Code »
WCF (
RSS)
Sorry, but there are no more tags available to filter with.
Right, so in Part 1 we looked at the requirements for a Discovery Service and in Part 2 we looked at how we'd host the WCF service. Now it's time to look at the UDP itself. First off though, if you look in Part 2 , at the declaration I've got for DiscoveryServer , you'll see I'm inheriting from a DiscoveryBase . This base class will handle most of the UDP stuff, since both DiscoveryClient and DiscoveryServer need a very similar set of operations. Let's look at the most important...
Right, so in Part 1 we looked at an overview of how this discovery system should work. Now let's start looking at specifics. Before we start diving into the UDP stuff, let's look at the information that the server will publish and how this will be accomplished. If you recall, the mechanism I suggested was that the server host a normal WCF service that held the information about the services, and that the UDP would be used to provide access to this service. So let's start with the WCF...
Metadata Exchange mechanisms such as WSDL are all very well and good, but they fulfil one part of the automatic discovery experience. If you look at WCF a service consists of three parts: Contract Address Binding So, Metadata Exchange helps you figure out the Contract if you're given the Address and sometimes the Binding. All very well and good for assisting us developers get running in using a service. However, how about a scenario where you already know the Contract but you need to figure out...