@Ypar
Apart from informaiton provided by Jirapongse, there are some information from Data Notification page mentioned aboutThomson Reuters Elektron real-time network, RICs may now be created with up to 32 characters (17 character in the old IDN network). It's information from DN085020.
The answer is in this question.
Moreover, the maximum size of name attribute in the request message of Elektron API is 255 bytes which is the same as TREP.
@moragodkrit.chumsri_1Are these the conceptual limits of current RICs, or the limtis of various APIs?From the doc references it seems to indicate that it is both, but it is not clear.
I am really looking for the conceptual limit on the length of a RIC. Ideally with an example of a super long RIC.
As the RICs may be created with up to 32 characters on new Thomson Reuters Elektron realtime network. It should be the conceptual limit of current RICs for the system or application which want to send or recieve data through the network.If you want to publish super long RIC which has RIC size more than 32 character, it may not work on Elektron Realtime network.
But if your application is just designed for direct communitcation between your own Publisher and Consumer application, length of RIC name could be over 32 characters and it depending of the size of data structure API used to hold RIC name.
For example,
In EMA C++, it uses EmaString to keep RIC name and the size limits to MAX_UINT32 accroding to header file EmaString.h.
Using custom RIC name, please make sure the existing applications/System/APIs involved are capable of handling it.
@Ypar Why the need to know this one may ask?
Remember that TREP is data feed agnostic. The limit for the data item name in general is 255 chars as stated in current thread by jirapongse.phuriphanvichai. However, any given feed use some form of naming convention for the items the feed publishes. For example, feeds from Thomson Reuters use the RIC naming convention which by design limits itself to 32 chars. Other feeds use other naming conventions.
If you lock yourself into 32 chars then your application will indirectly be crippled and can only ever safely consume feeds that use the RIC naming convention (or another naming convention with similar length restrictions).
I would argue that the limit you are looking for is 255 chars, not 32 chars. But if your question is read verbatim then the correct answer is 32 chars.
@Lars-at-Addicticks I was not looking for the limit of the data structures or protocol, that is clear enough. The application is limited in scope and will only consume RICs from TR. I actually don't need the max, something that can cover 99.99% of cases would do, but it's easier to ask for the max.
