To group together objects into types, the server makes an RPC library call repeatedly to associate whatever objects it expects will appear in incoming RPCs with a type UUID. The association is made between each of the expected incoming object UUIDs and the type UUID. The following is an example:
rpc_object_set_type(obj_uuid, type_uuid, &status);
A type UUID is nothing but a special kind of object UUID. Type in this context refers to a group of ordinary object UUIDs that have all been associated with another specially generated common object UUID, which can then be used to identify that group of objects collectively.
The type UUIDs in turn are associated with the entry points of manager modules in the server when the server registers with DCE. An incoming RPC with a typed object UUID in its binding will be automatically vectored by the server's runtime to the appropriate associated type manager.
Note that it is not necessary to call rpc_object_set_type( ) at all if you intend to register only one set of manager routine implementations per interface.