1. API:EMA 220.127.116.11
We have a question regarding to the way we download the data from RTDS.
As you know, we have to manage different type of data in term of availability such as real time, CLS, DLY, D10, D15, D20, D30, D6h,…
For the moment the push time is calculated at the start of the program by an SQL. E.g. ASIA with Push time = Snaptime +20, EU with Push time = Snaptime + 15
We believe that this may limit us in the future in the event of new delayed times.
We would like to work in a more dynamic way. However we fear this way of working will be less robust.
The idea would be to wait to receive the Data (Onrefresh from the API) to determine the Push time.
So this means the program will have to launch a minutely scheduled task which determines every minute if the Push has been reached (precise scheduling not possible).
Do you have any advice on this?
Is there a way to know, during the subscription process, all the different delayed time associated for the instruments belonging to a specific group (e.g. ASIA)?
Thanks in advance for you follow-up,