groupId RsslBuffer type to std::string

Below is Description of groupId:

The groupId with which this information is associated.
This is typically represented as a series of 2-byte unsigned integers
(i.e. two-byte unsigned integers written directly next to each other in
the buffer). The example provided in the RANGE / EXAMPLE
column of this table shows such a series, with inserted dots to help
indicate two-byte value. When encoded into a buffer, do not include
dots.

What is the proper way to copy/convert groupId into std::string so that groupId be stored and logged with human readable format?

I have tried the following:

const std::string groupId{msg->refreshMsg.groupId.data, msg->refreshMsg.groupId.length};

const std::string_view groupId{msg->refreshMsg.groupId.data, msg->refreshMsg.groupId.length};

Find more posts tagged with

elektron

rssl

elektron-sdk

refinitiv-realtime

elektron-transport-api

eta-api

rrt

Accepted answers

nick.zincone

Hi @tinmyo.win,

The buffer can contain a series of 2-byte blocks, in network byte order, representing the groupID. As such, try iterating through the buffer and assigning the 2 bytes into an unsigned short. That is

Note: ETA also has an example of how they dump the groupID using the 'xmlDumpMsgBegin' function.

Here is an example of the output from above:

All comments

nick.zincone

Hi @tinmyo.win,

The buffer can contain a series of 2-byte blocks, in network byte order, representing the groupID. As such, try iterating through the buffer and assigning the 2 bytes into an unsigned short. That is

Note: ETA also has an example of how they dump the groupID using the 'xmlDumpMsgBegin' function.

Here is an example of the output from above:

tinmyo.win

Thanks for the code snippet. I am able to extract groupId correctly now.

Can you please also point me to how to create RsslBuffer with different length of groupId? The reason is transport API document states that a consumer needs to handle group Id with variable length such as "1.26.102". We requested different security type and different symbols but we have seen only group Id response with single 2-byte integers. We would like to create test cases with groupId, that has series of 2-byte integers.

nick.zincone

Hi @tinmyo.win,

EDIT: The answer below was based on testing against an EMA IProvider Training example that set the group ID. However, through further testing, it appears the example does not properly assign the group ID based on network byte order. I will need to confirm with the development team. Please refer to the first answer above for the actual algorithm to process the group ID.

First thing, I updated my answer above to correct the algorithm to properly extract the 2-bytes and store within an unsigned short. Instead of:

unsigned short id = (groupId->data[i] << 8) | groupId->[i + 1];

It now reads:

unsigned short id = (groupId->data[i] | groupId->[i + 1] >> 8);

To create a test case that has a series of 2-byte integers, one way is to utilize one of the EMA IProvider Training examples, specifically 250__GroupStatus__Fanout. In there, you can modify the code to add additional groupIds. For example, I defined a new ID called: 'secondaryGroupId = 19', i.e.

You can add as many as you want to test. Then I simply added the following line within the AppClient::processMarketPriceRequest() method:

You can then take your ETA consumer application and test it against this Provider and you should see 2 ID values (10 and 19) displayed.

tinmyo.win

Hi @nick.zincone, we have been strictly using Eta API and sink_driven_source + ADS as our provider. Is there anyway we can create groupId RsslBuffer with Eta API?

tinmyo.win

is anything wrong with ?:

unsigned short id = (groupId.data[i] << 8 | groupId.data[i+1]);

I am unable to parse group ID with updated answer you have provided below:

unsigned short id = (groupId.data[i] | groupId.data[i + 1] >> 8)

EXPLORE OUR SITES