Changes between Initial Version and Version 1 of Ticket #7363, comment 3


Ignore:
Timestamp:
2015-05-24T22:44:59+02:00 (9 years ago)
Author:
A_Pirard

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #7363, comment 3

    initial v1  
    1 I didn't know that this bug exists when I wrote the following, another phrasing, to which I add "reproducing":
     1I didn't know that this bug report existed when I wrote the following, another phrasing, to which I add "reproducing":
    22I often notice with an often non-responding server that JOSM doesn't use its WMS cache.
    3 I mean, if one is returning to previous work when the server no longer responds, that WMS first displays previously cached tiles, that it probably sends requests that time out for the same tiles and that it paints them in red. That's how it looks like.
    4 That is of course frustrating to see that one could but cannot finish some work because of that.
     3If one is returning to previous work when the server no longer responds, WMS first displays previously cached tiles, then it probably sends requests that time out for the same tiles and it ends up painting them in red after a delay. That's how it looks like.
     4That is of course frustrating to see the map eased and that one could but cannot finish some work because of that.
    55
    66Reproducing:
    … …  
    88Close and restart JOSM.
    99Reload the same OSM area.
    10 Disconnect the Internet (e.g. shutdown WiFi or sudo route add default gw 127.0.0.2 (later: sudo route del default gw 127.0.0.2))
     10Disconnect the Internet (e.g. shutdown WiFi or sudo route add default gw 127.0.0.2 (restore later: sudo route del default gw 127.0.0.2))
    1111Reopen the same WMS layer: tiles appear and then turn to red after a timeout.
    1212Cheers.