Hardcoded limits in ETA consumer example application

howard.kidd

The ETA consumer example application has fixed limits for many of the items coming back in the RSSL messages.
If for instance there are more services in the directory service response than the application can handle it simply errors.
Or if a particular string length is larger than it is expecting it simply errors

Are there any actual limits and if so are they documented anywhere, as an example what is the maximum number of services that can be returned in a source directory refresh

zoya faberov

Hello @howard.kidd ,

Believe that you are referring to Examples\Common\rsslDirectoryEncodeDecode.h:

...
#define MAX_CAPABILITIES 10
#define MAX_QOS 5
#define MAX_DICTIONARIES 5
#define MAX_GROUP_INFO_LEN 256
#define MAX_DATA_INFO_LEN 1024
#define MAX_LINKS 5
#define MAX_SOURCE_DIRECTORY_SERVICES 15
#define MAX_SRCDIR_INFO_STRLEN 256
...

If this is the case,

These limits are defined for the purposes of the example, to show how to process source directory information and are not enforced by ETA API. However, in my experience, the definitions are realistic, and in most cases should cover the corresponding aspects of a production RTDS.

In terms of the due diligence, if you are connecting to a local RTDS and there is any doubt, you may wish verify with local market data group/admin, what are the corresponding aspects of your local RTDS, to make sure the limits defined by your application design are not exceeded.

Hope that this information is of help