Collaboration diagram for RtecEventData:
|Add padding to align the octet sequence contents. |
|Octet sequence payload. |
|Use a CORBA any type as payload. |
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.
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:
Octet sequence payload.
This is the payload used more often by high-performance applications.