Dear All, I am contacting the Geoserver mailing list, since I have not received an answer from the GeoWebCache mailing list.
We are about to improve our GeoWebCache workflow and would like to ask a couple of questions regarding the configuration and logging of the seeding process. The main goal of the workflow would be to archive up to date web-services by reseeding only tiles affected by recent changes. We are using the stand-alone-version of GeoWebCache and are able to calculate the changes inside the database resulting in easy to handle bounding boxes. Our main problem is, that there are some issues with the inhouse-network stability... As far as we know the seeding process is controlled either via a GeoRSS feed or through the Rest-API. In terms of best practice and stability, which way would you recommend? Is there any chance to track the success of the seeding and check if the tile-sets are complete? We tested both ways several years ago and missed a way to find out if the seeding was successfully completed. Thanks, Sonja Haas
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
