<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2013-04-09 23:00, Glenn Plas wrote :<br>
</div>
<blockquote cite="mid:5164817F.5030404@byte-consult.be" type="cite">On
04/09/2013 10:56 PM, Jo wrote:
<br>
<blockquote type="cite">I'm trying it out, of course.
<br>
It still seems to have the problem with the constant need of
having to use 'change resolution'. It would be great if that
could be solved as well somehow, but it may simply be a JOSM
problem as well.
<br>
<br>
Jo
<br>
</blockquote>
I'm still trying to fix some stuff, it seems every request is
generating a cache MISS due to the fact WMS is by definition not
to be cached. Cache-Control sent by AGIV server is 'private'
which complicates things (I have to get that header out and
replace it with some expirations).
<br>
<br>
I'm looking at MapProxy at this point, see
<a class="moz-txt-link-freetext" href="https://pypi.python.org/pypi/MapProxy">https://pypi.python.org/pypi/MapProxy</a> , it can probably do what
you ask.
<br>
</blockquote>
<a href="http://www.mapproxy.org/">www.mapproxy.org</a> mapproxy
nicely caches WMS in tiles. According to <a
href="http://mapproxy.org/support.html">Mapproxy mailing list</a>
and my own experience, its cache never expires (you must clean it up
"manually").<br>
You will be able to access your cache with WMS or TMS; that may make
a slight difference, but I expect nothing much to solve your
resolution change problem.<br>
I have made <a href="http://josm.openstreetmap.de/ticket/7563">comments
on the mailing list </a>including warning about inconsiderate
automatic resolution level changes. That problem is inherent to
JOSM and the same for all servers.<br>
<br>
Cheers, <br>
<br>
<table>
<tbody>
<tr>
<td valign="top">André.</td>
</tr>
</tbody>
</table>
<br>
</body>
</html>