|
dxFeed Graal Native SDK 3.10.0
|
The message event: a notification with an application-specific attachment. More...
#include <dxfg_events.h>
Data Fields | |
| dxfg_event_type_t | event_type |
| const char * | event_symbol |
| int64_t | event_time |
| void * | attachment |
The message event: a notification with an application-specific attachment.
It is neither a lasting nor an indexed event: messages are never conflated, its clazz is DXFG_EVENT_MESSAGE.
The attachment (the same for dxfg_configuration_t) is a UTF-8 null-terminated string (const char *, declared as void *) or NULL when there is no attachment:
So a non-string attachment loses its type when it passes through C: if the event is published back (or forwarded to another endpoint), the Java receivers get the string instead of the original object.
The C API does not support arbitrary Java attachments: C can neither create nor read them. For a string payload prefer dxfg_text_message_t and dxfg_text_configuration_t (TextMessage, TextConfiguration): their text is a plain string that passes both ways without loss.
Memory:
| void* dxfg_message_t::attachment |
The attachment: a UTF-8 null-terminated string (const char *) or NULL, see dxfg_message_t.
| const char* dxfg_message_t::event_symbol |
The symbol of the event (a UTF-8 null-terminated string) that belongs to the event and is freed with it.
| int64_t dxfg_message_t::event_time |
The time when the event was created, in milliseconds since the Unix epoch (UTC), or 0 if not available.
| dxfg_event_type_t dxfg_message_t::event_type |
The base structure: the fields of dxfg_event_type_t.