tr.txtI am making the following request using rmdsTestClient against sink_driven_source + ADS combination as provider:
./rmdstestclient -S hEDD -ct rssl -p 14001 -itemList IBM,AAPL.O,MSFT.O -X -l stdout
I received response for the symbols with groupID 1 and 2. Then I killed sink_driven_source to simulate service down or ServiceState = 0. I noticed that I received two RSSL_DMT_SOURCE updates for the two groupIds as dataState="RSSL_DATA_SUSPECT" followed by another RSSL_DMT_SOURCE update as ServiceState = 0. I have attached the XML response too.
My question is for source directory update, is it correct to assume that source directory updates are received in the order of GROUP level updates followed by SERVICE level update? Does that also mean that an Consumer application should clear all prior source directory information and react to source directory update as it comes?