EMA message deep copy and object reuse

f6c

RTO RTSDK/EMA Java

1. In the onUpdateMsg, What's the message object (and the data fields inside) reuse logic for the received updateMsg object? that is, at which condition or when the data fields in the previous received updateMsg will be re-used and populated to another updateMsg.
2. Regarding the deep copy in the onUpdateMsg:
   UpdateMsg copiedMsg = EmaFactory.createUpdateMsg(updateMsg);
   Do we have other high performance implementation recommendation so as to minimize the time cost on this to improve the throughput.

Thanks.

Jirapongse

@f6c

Thank you for reaching out to us.

1. The message object passed to onUpdateMsg must not be used outside the callback, as it may be reused after the callback returns.
2. The client can use view requests to specify the required fields, which helps reduce decoding time. In the callback, the application decodes the required data from the message object and then places the decoded data into a queue for processing by another thread.

Clients can refer to the EMA Java Performance Tools documentation (EMAJ_Perf_Tools_Guide.pdf) and the examples provided in the package, which are available as buildable open-source projects and demonstrate best practices and performance-oriented coding for the respective APIs.