Andreas Schmitz wrote >> The service provider is much bigger authority than I. They say this way gives >> them a possibility to separate the requests on different servers for sharing >> the load in the future. I don't believe really that sending GetCapabilities >> is >> so extra heavy computitional task that it would ever deserve a dedicated >> server but this is the way they have decided to use and that's it. I will >> try >> to cascade the service through Mapserver, it should lead to a normal looking >> WMS service that could be accessed with OpenJUMP.
> ok, that looks like another valid scenario. Although I'd agree that > GetCapabilities-requests are usually not a performance burden ;-) I started to think that it actually gives a simple way for dealing more heavy GetMap requests as well. When answering to GetCapabilities request the system could inform that the first client should ask further service from WMS_1, the next from WMS_2 etc. in a round robin way. All what the users should know in the beginning is the contact point address to GetCapabilities. Is sounds so simple that it might even work. Anyway, I am sure OpenJUMP is not the only WMS client that does not support this. -Jukka- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
