11-02-2025 08:29 PM
I am using a shared variable (boolean) between two independent applications, A and B.
Application A writes to the variable, while application B reads from it, and we can configure a timeout for the read operation in B.
The timeout flag only becomes True after B initiates the read and the specified timeout period elapses.
If B reads the value for the first time a long time after A has written it, B retrieves the stale value that still remains on the network.
However, there is no timeout setting available on the write side in application A.
Question: How can we configure the system so that B discards data written by A a long time ago?
Using a full flush operation might work, but we are concerned that it could affect other shared variables in the system.
Thank you for your guidance.
11-02-2025 09:21 PM
I don't really understand what you are talking about.
Bob Schor