Exporting to the RPC Name-Service Database

After specifying the protocol sequence and endpoint and registering any dynamic endpoints in the endpoint-map database, the server application registers the binding handle for the interface with the RPC name-service provider by calling RpcNsBindingExport.

In the Microsoft environment, the server application should register itself with the name-service database every time the server application is run. In the OSF-DCE environment, the server application registers with the name-service database only once and that is when the application is installed. The Microsoft Locator maintains its database in transient memory on the server, while the OSF-DCE name service resides in permanent, replicated storage which is relatively expensive to update.