Hi, besides all this i think you are also running into the maximum usable parallel requests a browser can do by default. The maximum is depending on your browser and in some browser you can configure this in the browser settings. The alternative is to put your WMS server behind different names. You can for example route www.example1.com<http://www.example1.com> and www.example2.com<http://www.example2.com> both to your server and configure openLayers to use an array of baseUrl's
Hope this also helps Cheers Kris Met vriendelijke groet, Kind regards, Kristiaan Geusebroek Consultant [cid:[email protected]] [cid:[email protected]] Email: [email protected]<mailto:[email protected]> Tel: +31 (0)35 538 1921 Fax: +31 (0)35 538 1922 Mobiel: +31 (0)6 3069 7223 Utrechtseweg 49 1213 TL Hilversum The Netherlands http://www.xebia.com<http://www.xebia.com/> Xebia Blog: http://blog.xebia.com/ Xebia Podcast: http://podcast.xebia.com/ On Sep 13, 2010, at 8:05 PM, Tim Schaub wrote: If you really have to have many layers dynamically rendered, I think your best bet will be using a single WMS layer with a list of layer names. It sounds like your reason for not doing this the behavior of the OpenLayers.Control.LayerSwitcher. If you can put a bit of time into a custom control for your application, it shouldn't be hard to create checkboxes for your layers. For each checkbox, add an onchange listener that compiles the list of visible layers and updates the layer. layer.mergeNewParams({layers: visibleLayersList}) If that won't work for you, other sensible options are: 1) change layer.buffer to 0 2) increase layer.tileSize or set layer.singleTile true Andreas Hocevar gave a nice presentation at FOSS4G that covered these and other options. See his examples here: http://ol-performance.appspot.com/ On 9/13/10 11:55 AM, Planet)x wrote: I am having problems using tilecache it just won't work with our environment. We are using Intergraph Geomedia Webmap products and I have created a site with many WMS Layers (each of my WMS has a single layer). I did this because our site now allows users to display/turn off individual layers so we didn't want to have a group of all layers we need each one to be individual so the layerswitcher can turn them off. Well my approach is very slow half the time no layers will load when I load the page, other times they all load but most of the time only a few of them load properly and I have to reload my page multiple times to see it. I have tried implementing tilecache but our network admin has our server pretty locked down and I think it is not working because of this. Is anyone else using Geomedia and has a different approach to this? I know theres obviously something I should be doing different than declaring a new WMS layer for each layer because it is very slow. All other openlayers examples I have seen I can pan around/zoom in and out and it is reasonably fast but it seems like any zoom operation I perform on my own just redraws and does a request again for every single layer. Any suggestions on how to improve this speed or what I am doing wrong greatly appreciated. -- Tim Schaub OpenGeo - http://opengeo.org Expert service straight from the developers. _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
<<inline: image005.jpg>>
<<inline: image006.png>>
_______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
