The Sametime Embedded Client currently does not provide a built-in capability to detect certain configuration or directory information changes and automatically invalidate or refresh the cached information. As a result, the client may continue to use outdated information stored in the local Sametime cache.
When the affected cache file is identified, the current workaround is to manually delete the cached file, for example through a script. This allows the Sametime Embedded Client to regenerate the cache using the updated directory information. However, this approach requires additional administrative effort and is not an ideal long-term solution.
Provide a built-in feature in the Sametime Embedded Client, integrated with the Notes client, to manage and invalidate local Sametime cache information.
This functionality would eliminate the need for custom scripts to manually delete cached files and would provide a more reliable and manageable way to ensure that the Sametime Embedded Client always uses current directory and configuration information.
A built-in cache management mechanism would reduce administrative overhead, eliminate dependency on custom cleanup scripts, and help prevent issues caused by stale Sametime directory or configuration information. It would also make troubleshooting and deployment of configuration changes more predictable for environments using the Sametime Embedded Client with the Notes client.
