Represents an object which the plugin can use for calling back to access some data and functionality provided by the process that uses the plugin.
To use this object, request an object implementing a particular I...UtilityProvider via queryInterface(). All such interfaces in the current SDK version are supported, but if a plugin intends to support VMS versions using some older SDK, it should be ready to accept the denial.
NOTE: Is binary-compatible with the old SDK's nxpl::TimeProvider and supports its interface id.
std::string nx::sdk::IUtilityProvider0::homeDir |
( |
| ) |
const |
|
inline |
The dynamic library of a Plugin can either reside in the directory designated for all plugins, together with other plugins, or in its subdirectory containing the dynamic library and potentially other files (which are ignored by the Server), e.g. other dynamic libraries the Plugin depends on, or some resource or configuration files that are loaded at runtime. If a Plugin resides in such dedicated subdirectory, it is called Plugin's Home Directory. Its name must be equal to the Plugin's libName - the name of the Plugin dynamic library without the lib
prefix (on Linux) and the extension.
- Returns
- Absolute path to the Plugin's Home Directory, or an empty string if it is absent.