Custom adapters
The custom adapters interface makes it possible for users to develop
adapters with as much functionality as those provided with the product.
Developing custom adapters The custom adapters interface makes it possible for users to develop adapters with as much functionality as those provided with the product.
Adapter registration and the library virtual table The first step required to develop an adapter is to add the adapter to the adapters.xml registration file.
Initializing the adapter InitializeLibrary provides an entry point by which any global structures, critical sections, or lists that are required by the adapter can be initialized.
Point to adapter methods After your adapter is loaded, you call the virtual table (vtable) structure to obtain pointers to the methods.
Adapter registration file The adapters.xml registration file contains a single tag for each adapter, including a number of attributes to provide information about the adapter.
Additional adapter methods There are a number of additional methods that are part of the HIP Programming Interface library that are of particular relevance to adapter developers.
Passing data to and from maps Data is passed between adapters and the engine through stream objects. From the adapter perspective, there is no need to create these stream objects; they are already created when either the Get or Put method is called.
Threads, connections, and transactions overview It is important to understand how threads, connections, and transactions interact.
Have feedback? Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.