Publishing with Windows Sockets Registration and Resolution (RnR)

Microsoft® Windows® Sockets services can use the registration and resolution (RnR) APIs to publish services and look up services so published. RnR publication occurs in two steps. The first step installs a service class that associates a GUID with a name for the service. The service class can hold service-specific configuration information. Services can then publish themselves as instances of the service class. Once published, clients can query the directory service for instances of a given class using the RnR APIs and select an instance to bind to. When a class is no longer useful, it can be removed.