|
|
After defining the object class with the definition tables, the OSAs must bind the definitions to Server API, so it can call the appropriate execution procedures correctly, and do basic type checking on passed attributes and data.
Binding also provides the writer of the OSA with the ability to pass a handle to the Server API. This handle will be returned to any execution procedure or request processor that belongs to the current class when it is called. By use of this handle, the OSA writer can store class-specific database information when multiple classes all use the same execution procedures.
You can bind class definitions with the function OFBinding, which causes Server API to load the class definition tables. The Tcl interface is described in OFBinding(3tlib), and the C/C++ interface in OFBinding(3sadm). When calling the binding function, the OSA can specify whether it will be using the default request processor (faster and built into the Server API) or one that the OSA will provide.
For more information, see ``BMIP request processor'' and ``Example request processors''.