TAO_RTEvent
2.3.1
|
User defined Event Data. More...
import"RtecDefaultEventData.idl";
Public Attributes | |
long | pad1 |
Add padding to align the octet sequence contents. More... | |
EventPayload | payload |
Octet sequence payload. More... | |
any | any_value |
Use a CORBA any type as payload. More... | |
User defined Event Data.
This structure defines the default payload in TAO's Real-time Event Service.
Users wanting maximum flexibility can use an Any, users that only have one type of event may use structures, other users may preffer union, trying to strike a balance between performance and flexibility. Users willing to implement their own marshalling may use a sequence of octets.
The Event Service is completely transparent as to the contents of this structure.
any RtecEventData::any_value |
Use a CORBA any type as payload.
long RtecEventData::pad1 |
Add padding to align the octet sequence contents.
This fields ensures that the contents of the octet sequence following are always aligned to an 8-byte boundary. Such alignment allows application developers to implement custom demarshaling from the octet sequence without requiring any data copies.
This is how this works:
EventPayload RtecEventData::payload |
Octet sequence payload.
This is the payload used more often by high-performance applications.