Hello Masoud,
I have tested the following scenario using qRFC.
1. I check how many entries are in TRFCQOUT for my channel.
- If more than 2, i do nothing.
- If not, i trigger an outbound qRFC, i.e. generate one entry.
2. Inside this qRFC, first I wait some (5) seconds.
3. Then I read the last update (field update_start) time stamp from my own Z-table.
4. Then I update field update_start with new time stamp. Do commit.
5. Next I extract the delta for the data (now - last update p.3).
6. Then I prepare the data and send it to the front-end.
7. Finally I update the finish time stamp (field update_finish).
(One can see that probably this field is not used, but it will be useful when you need to identify the failed channel updates. In this case: update_finish < update_start )
It seems to work OK. Why do you think that qRFC do not provide the a guarantee regarding the execution time of the tasks? In my case it will be delivered in 10 seconds maximum, even if there were 1000 updates in between...
And another question, I used my own Z-table to store the information regarding APC requests, do we have something similar in the standard maybe?
Thanks, Dima