In time for GeoServer 1.7.2 , GeoWebCache 1.0.1 has been released.
No bugs have been reported since the release of 1.0.1. The RESTful interface and use of XStream have been reengineered a bit to accommodate new configuration options more easily.
Quick summary:
- Support for proxying Google Maps, Virtual Earth and Mobile Google Maps clients without caching (see below)
- Backend timeout is configurable
- XStream is now centered around a GeoWebCacheConfiguration? object instead of separate layers.
- The RESTful interface has been reengineered, following the path that David Windslow staked out for GeoServer's rest module.
- The RESTful interface relies on the extension in the URL, such as .xml , instead of the content type of the request. See the documetation
Updating:
If you have modified geowebcache-servlet.xml you should use the new file and forward your changes. In many cases this will only require you to update the URL to the getcapabilities document.
If you want the XSD parser to take a careful look at your geowebcache.xml configuration file you should change the namespaces from 1.0 to 1.0.1, else it will complain that i cannot find the gwcConfiguration element.
If you are building your own, make sure to get the 1.0.x branch rather thank trunk. The changes under the hood are quite substantial, I will probably end up copying back to trunk rather than merging.
Changes:
The main new feature is that you, either globally or for individual layers, can enable the Google Maps, Virtual Earth and Mobile GMaps services to proxy requests without caching. This is handy if you want to display live data, but your WMS server does not support these clients natively. The two parameters are cached=false and metatiled=false. The latter parameter determines whether to use tiled=true when forwarding the request to the backend, independent of the layer configuration. On servers such as GeoServer this will reduce the number of duplicate labels.
For these parameters to work you need to set <cacheBypassAllowed>true</cacheBypassAllowed>, either for the layer or for the entire configuration. Layers that are automatically configured from WMS getCapabilities documents will default to true unless you change the last construction parameter in the bean constructor.
The second new feature is that you can configure the <backendTimeout> in seconds, again per layer or globally. The default is 120 seconds, the amount of time a WMS server can spend before the connection is closed.
Looking forward:
- Some work has gone into supporting that certain parameters can be modified. This work will hopefully pick up momentum this week.
- There is a separete effort to support just the TIME and ELEVATION parameters. See ticket 67
- Amazon S3 support is slated for inclusion, but seems more appropriate for 1.1. Patch at ticket 63 , probably works with 1.0.1 too.
