You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Tile Cache is based on the URL of the image inside. This doesn't work well for cases where the URL can vary, for example if there are multiple instances of the server and the URLs are distributed randomly between them (like s1.maps.example.com and s2.maps.example.com).
This can be handled in the Factory Info (so that it always returns something like (x + y) % number_of_servers), but I think the cache shouldn't rely on uniqueness of the URLs and instead should be based on the X, Y, zoom and mapId fields.
The text was updated successfully, but these errors were encountered:
Yeah, the whole solution in general is not ideal for this scenario. I'll have to think a bit more on that, but it'll probably be a regex to match the server URL.
A proper solution would be to activate the caching only for those few connections that load tiles. If you're up for implementing that, let me know (PR).
Currently, the Tile Cache is based on the URL of the image inside. This doesn't work well for cases where the URL can vary, for example if there are multiple instances of the server and the URLs are distributed randomly between them (like
s1.maps.example.com
ands2.maps.example.com
).This can be handled in the Factory Info (so that it always returns something like
(x + y) % number_of_servers
), but I think the cache shouldn't rely on uniqueness of the URLs and instead should be based on theX
,Y
,zoom
andmapId
fields.The text was updated successfully, but these errors were encountered: