The OpenROAD Server uses a generalized method signature so that you do not need to construct and deploy separate proxy/stub code for customized COM signatures for each OpenROAD 4GL procedure. The data passed through this signature is dynamically mapped to the actual signature of the called 4GL procedure.

This generalized signature provides an easy-to-deploy baseline facility, which is the only interface directly supported by the OpenROAD Server. Developers may also build their own customized COM objects and method signatures to wrap the underlying interface.