[OSM-dev] Removing functionality and giving just No as answer

Yves yvecai at gmail.com
Wed Mar 8 17:37:42 UTC 2017


It's like the close door button in an elevator, you know it usually does not speed things up, but it feels good to press it anyway. 
Yves 

Le 8 mars 2017 13:03:32 GMT+01:00, Tom Hughes <tom at compton.nu> a écrit :
>On 08/03/17 09:35, joost schouppe wrote:
>
>> While a lot of the comments are a bit misguided, I think it is clear
>> that quite a few mappers use this dirty trick to get the render to
>> refresh. As OSM.org is supposed to be a mapper's tool and not a
>general
>> public website, I think it is quite obvious that a
>forced-tile-refresh
>> function is within the scope of the website.
>
>There is a cargo cult belief that you need to force dirty the tile at 
>the renderer but that is almost never the case - any changes to nodes 
>and ways will automatically dirty the relevant tiles. Only changes to 
>relations are not handled automatically.
>
>Now there was a bug for much of last week where that wasn't happening 
>properly - that was fixed on Friday morning and all the missed tile 
>expiries were processed over the next 24 hours.
>
>What is normally an issue is the squid caches that sit in front of the 
>renderers, but a simple shift-reload will bust those caches and in fact
>
>a manual dirty will do nothing at all to help with those.
>
>Tom
>
>-- 
>Tom Hughes (tom at compton.nu)
>http://compton.nu/
>
>_______________________________________________
>dev mailing list
>dev at openstreetmap.org
>https://lists.openstreetmap.org/listinfo/dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20170308/9adf50ee/attachment.html>


More information about the dev mailing list