MessengerIOServer Class
The MessengerIOServer handles transfer of signals and properties between applications. More...
| Header: | #include <MessengerIOServer> |
| Inherits: | IOServer |
Additional Inherited Members
- 32 public functions inherited from IOServer
- 92 public functions inherited from CDPComponent
- 39 public functions inherited from CDPObject
- 49 public functions inherited from CDPBaseObject
- 27 public functions inherited from CDP::StudioAPI::CDPNode
- 22 public functions inherited from CDP::StudioAPI::ICDPNode
- 2 static public members inherited from CDPComponent
- 6 static public members inherited from CDPObject
- 1 static public member inherited from CDPBaseObject
- 1 protected function inherited from IOServer
- 12 protected functions inherited from CDPComponent
- 15 protected functions inherited from CDPObject
- 1 protected function inherited from CDP::StudioAPI::CDPNode
- 8 protected variables inherited from IOServer
- 31 protected variables inherited from CDPComponent
- 7 protected variables inherited from CDPObject
- 8 protected variables inherited from CDPBaseObject
- 1 static protected member inherited from CDPObject
Detailed Description
The MessengerIOServer handles transfer of signals and properties between applications.
Property and signal connection and disconnection is handled automatically, and signals are made to flow between the correct applications at (at least) the wanted rate.
Usage
The MessengerIOServer is an autonomous component that is instantiated in the default configuration. It can not be instantiated directly, and there should only be one MessengerIOServer instance in an application.
Note: The MessengerIOServer should not be used by end-user code, and this documentation is here for consistency only.
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.