Flushes all internal caches held by the custom dataset.
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 ICustomDataSet 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.
public void FlushCache ()Windows, Linux, Android
In this article
Flushes all internal caches held by the custom dataset.
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 ICustomDataSet 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.
public:
virtual void flushCache ()Windows, Linux, Android
In this article
Flushes all internal caches held by the custom dataset.
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 ICustomDataSet 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.
public abstract void flushCache ()Windows, Linux, Android
In this article
This element is not available using the selected API.
In this article