This topic presents a summary of the dispatcher service functions:
The following functions enable you to register service managers and services with the dispatcher. Both of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Registers a service with the dispatcher at initialization time. | |
|
Registers a service manager with the dispatcher at initialization time. |
The following functions are used to access the event queue. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Retrieves the queue handle of the specified context. | |
|
Creates an event and sends it to the application event queue or to the dispatcher event queue. | |
|
Queues events to other services or applications. |
By modifying associated parameters, you can alter the characteristics of many Natural Access services. The following functions enable you to obtain or change parameter information. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Verifies the existence and returns the value of a parameter field or structure. | |
|
Retrieves the value of parameter field or structure specified by name. | |
|
Returns parameter values for a specified parameter structure. | |
|
Permanently modifies the value of a default parameter. |
Service SPI functions call dispSendCommand to send commands to the service implementation. This function is synchronous.
The following functions enable you to create, modify, and destroy service API handles. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Associates a handle with a Natural Access context or object descriptor. | |
|
Creates a client-side API handle and associates it with a server-side object handle. | |
|
Destroys the API handle and clears its associated value. | |
|
Returns the client-side handle associated with a server-side handle. | |
|
Returns the client-side handle associated with the name of a service object. | |
|
Retrieves information associated with a client-side API handle: context handle, server-side service object handle, and service identifier. | |
|
Retrieves all information associated with a client-side API handle: context handle, server-side service object handle, service object name, and service identifier. | |
|
Associates a server-side object handle with a client-side API handle. | |
|
Associates a service object name with a client-side API handle. | |
|
Adds a command message to the context's dispatcher queue. |
The following functions enable service managers or services to associate wait objects with Natural Access queues. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Returns an internal wait object representing the operating system-specific wait object. | |
|
Registers wait objects and their processing functions with a Natural Access queue. | |
|
Unregisters wait objects and their processing functions from a Natural Access queue. |
The following functions enable you to control service error logging and tracing. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Invokes a user defined error handler, logs a trace message, and returns the error code. | |
|
Logs an error to the Natural Access trace log. | |
|
Retrieves the address of the global trace mask at process initialization. | |
|
Logs a trace message and buffer to the Natural Access trace log. |
dispGetText returns the text representation of errors, reasons, events and commands. This function is synchronous.
The following functions aid service developers in the use of data buffers within the Natural Access client-server development environment. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Allocates buffer of memory managed by the Natural Access dispatcher. | |
|
Releases a buffer of memory managed by the Natural Access dispatcher. | |
|
Designates a command buffer as being used for asynchronous input. | |
|
Designates a command buffer as being used for asynchronous output. |
The following functions enable service managers to use the dispatcher runtime control mechanisms. All of these functions are synchronous:
|
Function |
Description |
|---|---|
|
Requests that a service action be invoked when a runtime control condition occurs. | |
|
Returns the runtime control conditions and actions that are registered on the Natural Access context. | |
|
Returns the number of runtime control conditions that are registered on the Natural Access context. | |
|
Returns the number of runtime control aliases added to the RTC database by services on the context. | |
|
Returns the runtime control aliases added to the RTC database by services on the context. | |
|
Registers an alias with the dispatcher to be associated with a service specific event. | |
|
Requests that the dispatcher's notification about a runtime control condition be removed. | |
|
Unregisters an event alias previously registered with the dispatcher. |
dispGetAppCtl returns information about default Natural Access usage by the application. This function is synchronous:
dispShutdown shutdowns or restarts either the Natural Access server (ctdaemon) or the system hosting the server. This function is synchronous.