Regarding your Item #1 – As I stated in my previous post the tiles get deleted even though ReadOnly is specified.
Regarding your Item #3 – The code I previously posted is the only code for caching that my application has. I am totally convinced there is an issue in MapSuite with not properly setting Creation Date as I have explained previously.
At first opportunity I will download the latest WMS Server build and test.
Please let me know what your developer finds after doing deeper research.
Our developer did further research, we double check the logic and build sample try to reproduce it about the ExpirationTime don’t works after the first time. It looks everything goes well, so we think that’s maybe related with your other code implementation.
The code that I previously posted is the only code I have for caching. Is this code correct? It’s the same code that’s in the example project you provided.
Are your tests under Windows 7 or Windows 10? I develop under Windows 10.
I am 100% certain this is not an issue within my application.
I will upgrade to the latest WMS Server deployment build and see if this bug has been fixed since version V9.0.0.856.
It looks the cache is in your transfer sever (WmsServiceEdition), and for this edition it should only contains the WmsRasterLayer but without the WmsOverlay.
I was merely pointing out that your client example uses WmsOverlay whereas my client uses WmsRasterLayer as a possible problem area.
In my posts I have mentioned Creation Date not being updated upon tile refresh. Would you please respond concerning Creation Date?
I setup a test where tiles were cached for two different extents. The expiration time of five minutes then elapsed. I then used Windows Explorer to manually delete the cached tiles on one of the extents. I then positioned the map client to said extent and the tiles were refreshed with the current date as the Creation Date.
When MapSuite does a tile refresh, on an existing set of tiles, the Accessed & Modified dates are updated correctly, but the Creation Date stays as the original date. Please speak to the fact that MapSuite, upon tile cache delete & refresh, does not update the Creation Date.
I just did some research and found this article.
Based on this article it would seem to me that MapSuite needs to be specifically setting the Creation Date after a tile refresh. Or, as previously suggested, use Modified Date to determine expiration/refresh interval.
I’ve just upgraded to ThinkGeo.MapSuite.WmsServer V11.0.0-beta002 and this issue has resurfaced.
You’ll see in this discussion thread that MapSuite repaired this issue in WmsServerEdition V9.0.0.1103.
You’ll recall the original issue was that after the timeout period (5 minutes) the issue was present. With WmsServer the issue occurs all the time (inside and outside the 5 minute timeout window).
My applications are using the following:
V11.0.0-beta107 ThinkGeo.MapSuite
V11.0.0-beta002 ThinkGeo.MapSuite.WmsServer
My post from yesterday->
You’ll recall the original issue was that after the timeout period (5 minutes) the issue was present. With WmsServer the issue occurs all the time (inside and outside the 5 minute timeout window).
Please check the MapSuite code again because the symptoms this time seem to be different.
Yes it’s a bug in MapSuite 10, in our PCL structure, it don’t return the UTC time but the cache logic used UTC time, so the cache tile expiration function don’t works correct.