[OpenLayers-Users] More than 20 wms layers, performance issues, geowebcache concurrency

[Sergeant_york]

As Phil Scadden stated, grouping the layers at serverside is a problem at
clientside since I have to be able to toggle on/off subgroups at client
side. For example if I grouped a,b,c together to abc layer, then if I close
"c" layer in the user interface what kind of process should be done?  

On the other hand I was thinking, these days hard disk spaces are huge so I
could group layers like a,b,c,ab,ac,bc,abc therefore when I merge new params
in the openlayers, requests will always find an answer from geowebcache. The
problem is group number count is (2^n)-1 where "n" is the number of
subgroups.  

Thank you for your answer. I was thinking maybe there is another option to
use which is already in openlayers to solve the problem or to increase the
performance of more than n layers in same map application(which was not
written in api documentation). Still all the answers inspired me so much :) 



--
View this message in context: http://osgeo-org.1560.n6.nabble.com/More-than-20-wms-layers-performance-issues-geowebcache-concurrency-tp4991740p4992850.html
Sent from the OpenLayers Users mailing list archive at Nabble.com.