Click or drag to resize

IpcClient Class (Typed)

Register an application as a client able to request and receive data from a designated server application.
Inheritance Hierarchy

Namespace:  XSharp.VO.SDK
Assembly:  XSharp.VOGUIClasses (in XSharp.VOGUIClasses.dll) Version: 2.19
 CLASS IpcClient INHERIT EventContext
Request Example View Source

The IpcClient type exposes the following members.

Public methodIpcClient
Construct an IpcClient object.
Public methodChangeData
Tell the remote server that some data value has changed. This results in the server receiving an IpcDataUpdateEvent. It is then the responsibility of the server to update itself.
Public methodCode exampleClientError
Handle ClientErrorEvent, if one occurs. Provide this event handler in your derived IpcClient class if you require special handling of errors.
Public methodDataUpdate
Called whenever the requested data changes. It is invoked after the IpcServer calls its UpdateTopic() method.
Public methodDestroy
Provide a method to de-instantiate an IpcClient object.
(Overrides Destroy.)
Public methodDispatch
Public methodExecute
Send a message to the server telling it to execute the command string remotely. As a result of this call, the server receives an IpcExecuteRequestEvent.
Public methodOverride
This is a compatibility method that is no longer used or needed.
(Inherited from EventContext.)
Public methodRequestData
Request updates on a particular topic from the server.
Globals and Defines
Public fieldoCargo
Cargo slot.
(Inherited from VObject.)
In X#, the IPC... classes provides a means of implementing DDE conversations between DDE-compatible applications. DDE (Dynamic Data Exchange) is a type of interprocess communication (IPC) that uses shared memory to exchange data between applications. IPC is governed by a DDE management library, an underlying DLL in Windows. In such a conversation, there is a client and a server. The client requests data from the server about particular topics and items, and the server supplies the requested data. The applications, after requesting to be a client or server (or both), then exchange updates as soon as new data becomes available. These exchanges are not necessarily initiated by the user. Each IPC client must uniquely identify the server with which it wishes to communicate, and then request data updates. After the initial transfer, the client is informed of any changes to the transferred data in the server by means of an IpcDataUpdateEvent.
See Also