We have a thread lock to ensure that updates from the same packet are processed together before a ServiceStateChange event can be decided.
The handlers locked solved a similar issue to #416
We should be able to eliminate the lock by changing out update_record for update_records to allow multiple records to be processed in one go and decide on a final ServiceStateChange event state.
We have a thread lock to ensure that updates from the same packet are processed together before a ServiceStateChange event can be decided.
The handlers locked solved a similar issue to #416
We should be able to eliminate the lock by changing out
update_recordforupdate_recordsto allow multiple records to be processed in one go and decide on a final ServiceStateChange event state.