Writing Your Own RPC Plugin

Write your own plugin to communicate with remotely callable procedures. This is useful if you want to call a remote procedure that does not use SOAP or HTTP protocols.

A general overview for writing a RPC plugin is below. See the SOAP and HTTP Plugins that provides for more examples. On Microsoft Windows, these are typically located in:

On UNIX-like operating systems, these are typically located in:

Every RPC plugin .dll or .so library file must contain at least three functions:

The .dll or .so file that contains these three functions can contain other functions as well. These often include additional functions called by the execute function.

It is recommended, but not required, that you use a separate .dll or .so file for each remote service. A single file may contain multiple sets of initialize, execute and shutdown functions, each of which is used for a separate service. Multiple services that share the same .dll or .so file can each use different initialize, execute and shutdown functions, or can share any number of these functions.

To write your own plugin, use an SDK. The SDK that supports RPC Plugins is Sybase CEP C/C++ SDK.

For more information see RPC Plugins