4. Designing and Writing OpenROAD Server Applications : How You Can Drive the OpenROAD Server from a Client : COM (Non-OpenROAD) Client Remote Server Object
 
Share this page                  
COM (Non-OpenROAD) Client Remote Server Object
A non-OpenROAD client has two alternative driver objects that lets a client connect to a desired OpenROAD application image, and to call 4GL procedures in that application image. These are the RemoteServer Object and the ASO Session Object. The first of these is implemented as an in-process server Dynamic Link Library (DLL) and registered under the COM PROGID OpenROAD.RemoteServer.
Methods
Methods provided by the Remote Server COM object include the following:
Initiate
Connect
GetInitiateParameters
CallProc
Disconnect
Terminate
Properties
Properties of the Remote Server COM object include the following:
AkaName
ImageFile
CmdFlags
Location
Routing
UseASOLib
PrivateOrShared
Options
Each of these methods and properties is described in the sections that follow.