The Resource API defines functions, structures, and macros that allow the Cluster Service to communicate with resources. The communication is indirect; the Cluster Service initiates requests with a Resource Monitor and the Resource Monitor passes them on to the resource. Status and event information are passed back from the resource DLL to the Cluster Service.
The following diagram shows how control flows from the Cluster Service through the Resource Monitor and a resource DLL to resources. The diagram shows four resource DLLs, three for Cluster Service resource types and one for a resource type defined by a third-party developer.
The Resource API consists of: