I’m using Elektron Transport C API 1.1.0 in Linux. Currently, the source directory messages are used only to identify service UP/DOWN messages.
The Consumer application in Elektron SDK doesn’t show how to use the different filters available in source directory messages.
The client application opens item stream from Elektron (ADS) end point for various asset classes(including international exchanges). Recently, we experienced an issue where the ADS dropped open streams due to maintenance and application didn’t receive item level status messages and the service didn’t go down. I was told that client application need to handle group status that comes in source directory updates.
As per my conversation with the Refinitiv support team, I’m interested in using all the filters available in source directory so that client application can recover from any failure that may happen in ADS and above.
Few things that popped up when reading the TransportAPIC80_RDMUsageGuide.pdf guide is below.
- How to use group id’s from item stream and source directory to handle group level notification ?
- How to use AcceptingRequests and Status from service filter ?
- How to use MergedToGroup information coming in group filter ?
Since the client application is using a low level ETA C API, is it recommended (and possible) to use Value Added API’s instead of the raw ETA C API ?
Is there any sample application or code you could point me as a starting point ?