Sadly I do not know how to close the client cache, do you know how that can be done? We tried the short expiring time and that just made it where the client cache had to be drawn again regularly. Needless to say, we do NOT want ClientCache. We have commented out the code for it and are NOT using the .ClientCache off of the LayerOverlay and we are using the .ServerCache only. What we have observed is that it appears that ClientCache still runs even with it not being used in our code. So my question is this, when using ServerCache, does it load the tiles from the server side and then loads/draws those tiles to the client?
From my observation it looks like Clientcache is still loading when only ServerCache is being used. This drawing process slows down the loading of the tiles, which are coming from the server. Here is a video showing the Diagnostic tools and our project loading the tiles https://www.screencast.com/t/xQR5s6ubUv5L. For reference, the server tiles are being loaded in since we put a "Test" on a few of the tiles server side. We have also made sure to clear out our Cache for the browser. Once the tiles are loaded for that zoom level returning to that zoom level the tiles load in fast similar to how ClientCache works https://www.screencast.com/t/qKNJConGZys.
Additional items of this observation.
When we have Client Cache on and we have the CacheID set to "TestingClientCache", the tile's src is
While when we do not have Client Cache on the tile's src is
They look rather identical outside the CACHEID.
As for the GenerateCacheImages, this process still has the same issues that I listed out above for ServerCache with the additional issue of drawing the tiles off center of where they are suppose to be. I will attempt to create a sample project for GenerateCacheImages for the off center issue.
Thank you for your help.