LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LVOOP DVR with non-blocking Dynamically-dispatched calls

With several parallel editors running race conditions are ALWAYS possible.  No matter what method you use for messaging, two editors making changes (Our software also has an API allowing code on other computers to make automated operations) can always lead to a race condition.  By using ONLy DVRs within the ditor I think the danger is severely reduced.

 

I need to revisit my code and refactor to see what it turns out like.

 

Either way, plenty to think about.

 

shane.

 

Ps The objects don't actually need to receive the CHANGE by notifier, queue oer event.  The simply need to receive that there WAS a change.  The rest they have already at hand via DVR.  Simply re-read the data and update their own local UI and hey presto.

0 Kudos
Message 21 of 22
(413 Views)

There is no real risk of race conditions because the Data is NOT sent with the update event.  Important is only that the actual update (Execution upon receipt of the event) is done after the changes have been made which we can guarantee easily.

 

Shane.

0 Kudos
Message 22 of 22
(367 Views)