Replies: 1 comment
-
Thanks for the suggestion. Although there does not seem to be any problem in the BitmapTileActivity sample.
Small (or edge) cases can not justify major interface changes (and maintenance). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Let me start with that I solved the issue in my local application already - now I want to ask, if you are interested in a PR.
Here is the situation: Some tile servers (like mapbox) will send you HTTP:200 but with an empty image [ContentLength: 0] when requesting none existing tiles - typically this happens, when you are at the north/south border.
While the complete system handles this situation quite well, I don't like the fact, that when I use a TileCache with my BitmapLayer, that the ZeroByte Tiles will be requested again and again. So even if this request will be handled fast & reliable - they are obsolete.
In my local implementation the TileCache will store in such a case byte[]{-1} for the requested tile and in return the UrlTileDataSource query method will call simply
sink.completed(TILE_NOT_FOUND);
and return when the TileReader indicated, that the content was just a byte[] of length 1 (with the value -1).The change includes interface changes in
HttpEngine
andITileCache
which might make this a bit messy.just let me know, if you are interested.
Beta Was this translation helpful? Give feedback.
All reactions