Try preloading WMS servers on startup

[Joern Ungermann]

A tedious first action is to get capabilities for the "usual" servers.

One might save a couple of manual clicks by trying to silently preloading servers in the lists. If user action (username/password etc) is requested, the server should not be loaded as the user might not want to load these.

Ideally, this loading would be made in a background task, but it might also be done in the startup.

The feature should be activated by the user in the configuration (similar to prefetching).

[Reimar Bauer]

We should first make a Performance Test where the time expensive part ist located. It can't be transfering of the XML document.

The next step is to verify that we can remove the get cababilities Button and to replace its functionality by selecting a server. Of course it makes much more sense to update all cababilities data by selecting a server and not to wait for a button clicked.

[Reimar Bauer]

We may want to have a list add Dialog And replace by this the Text edit list.

[Joern Ungermann]

This is not about speed, but more about doing the same task over and over again, i.e. automatization. Loading capability documents for two-three servers every time you start up MSS is annoying, especially for testing. This could be simply solved by a configuration parameter that preloads the capability documents upon startup. We have a lot of parameters that require editing the JSON file, and this fits the same role as many others.

[Reimar Bauer]

Add preloading capability to MSS

The patch adds a configurable preloading of WMS servers before the main application starts. Doing this in the background would be much better, but also more complex. The configuration parameter needs to be documented.

Fix issue #250

→ <<cset ce315f3cd344>>

[Reimar Bauer]

Removed a too verbose logging statement introduced for #250

See issue #250

→ <<cset c6651c4ace8d>>