Matti Viljanen wrote: > I think, based on gut feeling, that more accurate tile complexicity > indicator would be the size of downloaded OSM data in bytes... That > information would be easy to generate on-the-fly, when a client requests > a certain tileset. Or, is it possible to distinguish a tile download > from any other download? Or does it even matter on performance point of > view (to send it 'in vain', to e.g. JOSM)?
It might be a better indicator but then there are difficulties too: 1) The server has no database of tiles besides the files, so it cannot store downloaded tile sizes. 2) The client would need to communicate the downloaded sizes to the server so it would need to store that somewhere (the uploading client is not necessarily the rendering client) 3) AFAIK someone tested that a while ago: file size and downloaded .xml size correspond nicely, so the server might just as well take the information it has at hand. spaetz
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
