topic Re: TiledMapServiceLayer options in .NET Maps SDK Questions

TiledMapServiceLayer options

MauricioRamirez1 — Wed, 03 Apr 2019 20:40:39 GMT

We're experiencing a situation where the tiles for our basemap are not all coming through right away. When we run wireshark, we notice there are lots of 304 returns from the network proxy. Is there a way to force the requests not to be cached? Are we able to change the timeouts so that tiles can be re-requested when the 304 returns? We are using .net runtime 10.2.7

Re: TiledMapServiceLayer options

dotMorten_esri — Wed, 03 Apr 2019 21:31:59 GMT

304 returns should be fine. Why would those be an issue? (304 is basically just the server's way of saying "don't bother downloading the tile again - the tile you have in your cache is the same, so use that instead" and should make tile loading faster).

Are you sure the 304s are the reason some tiles are not all coming through?

Re: TiledMapServiceLayer options

MauricioRamirez1 — Wed, 03 Apr 2019 22:23:14 GMT

I'm assuming that's the case as I just opened the app and browsed to a random place I hadn't browsed to.

Re: TiledMapServiceLayer options

dotMorten_esri — Wed, 03 Apr 2019 22:41:09 GMT

The cache is the shared browser cache that all apps/browsers share, so could be the tiles was hit at a different time?
Alternatively your browser cache might be corrupt. Try blowing it away

Re: TiledMapServiceLayer options

MauricioRamirez1 — Thu, 04 Apr 2019 22:12:12 GMT

Tried blowing out the cache and still seeing the same. If the 304s are not the reason, what could be?