DiCE API nvidia_logo_transpbg.gif Up
API components

The functionality offered by the DiCE API is split into so-called API components.

Each component gives access to some aspect of the DiCE API. The basic interfaces mi::neuraylib::INeuray give access to these API components via their get_api_component() methods.

This page here lists all API components. Note that some API components are always available (e.g., configuration interfaces), while other API components are only available while DiCE is running (e.g. access to the database).

Interface always available
mi::neuraylib::ICache_manager_factory yes
mi::neuraylib::ICluster_manager_configurationyes
mi::neuraylib::ICluster_factory no
mi::neuraylib::IDatabase no
mi::neuraylib::IDatabase_configuration yes
mi::neuraylib::IDebug_configuration yes
mi::neuraylib::IDice_configuration yes
mi::neuraylib::IDistributed_cache no
mi::neuraylib::IExtension_api yes
mi::neuraylib::IFactory yes
mi::neuraylib::IGeneral_configuration yes
mi::neuraylib::IImage_api no
mi::neuraylib::ILibrary_authenticator yes
mi::neuraylib::ILogging_configuration yes
mi::neuraylib::INetwork_configuration yes
mi::neuraylib::INode_manager_factory yes
mi::neuraylib::IPlugin_api yes
mi::neuraylib::IPlugin_configuration yes
mi::neuraylib::IScheduler no
mi::neuraylib::IScheduling_configuration yes
mi::neuraylib::ITimer_configuration yes
mi::neuraylib::IVideo_codec_factory no
mi::http::IFactory yes
mi::rtmp::IFactory no
mi::bridge::IBridge_client no
mi::bridge::IBridge_server no