This method does not have to be thread-safe if it is only called implicitly by Carmenta Engine, either directly or by one methods defined in the ICustomOperator callback interface. However, if the implementation uses state that can be accessed or modified from some other thread then the implementation must perform the necessary synchronization to become thread-safe.

More details about thread safety and custom objects can be found in Threading model, custom objects.

This method does not have to be thread-safe if it is only called implicitly by Carmenta Engine, either directly or by one methods defined in the ICustomOperator callback interface. However, if the implementation uses state that can be accessed or modified from some other thread then the implementation must perform the necessary synchronization to become thread-safe.

More details about thread safety and custom objects can be found in Threading model, custom objects.

This method does not have to be thread-safe if it is only called implicitly by Carmenta Engine, either directly or by one methods defined in the ICustomOperator callback interface. However, if the implementation uses state that can be accessed or modified from some other thread then the implementation must perform the necessary synchronization to become thread-safe.

More details about thread safety and custom objects can be found in Threading model, custom objects.