Hi,<br><br>we were able to merge GDAL and WMS layer using your approach (third layer) with no problem. But we only used tilecache_seed.py for the third layer (against a different server instance). I didn't try to use on the fly serving of the third layer because of the loop-back :-). But shouldn't the loop back work also OK if you can restrict the external concurrent requests to one third of what the tilecache instance can handle? (Each external request can generate up to two child request towards the same instance.) I guess it also depends on your deployment. What's your deployment (standalone/mod_python)? And what's the behavior/error messages?<br>
<br>Tibor<br><br><br><br><br><br><br><div class="gmail_quote">2009/4/6 Gissur Þórhallsson <span dir="ltr"><<a href="mailto:gissur@loftmyndir.is">gissur@loftmyndir.is</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys,<div><br></div><div>I'm wondering whether anybody had tackled having multiple WMS servers as sources for a single tilecache layer?</div><div><br></div><div>I have two WM servers (one for raster data and another for vector data) which I want to merge into a single tilecache layer. I thought about creating a different tc layer for each and then creating a third one that uses the other two as sources(making the poor tilecache loop-back on itself), but I can't get it working.</div>
<div><br></div><div>Does anybody have any ideas I could try?</div><div><br></div><div>Kind regards from Iceland,</div><div>Gissur Þórhallsson</div>
<br>_______________________________________________<br>
Tilecache mailing list<br>
<a href="mailto:Tilecache@openlayers.org">Tilecache@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/tilecache" target="_blank">http://openlayers.org/mailman/listinfo/tilecache</a><br>
<br></blockquote></div><br>