About being stricter,
what do you think of locking down the WMS limits a little
bit by default for 2.0?
Not so much, something like:
- max wms request time: 1 minute?
- max memory used in a single request: 64MB?
- max error count: 1000
Not too strict but should avoid people restarting GeoServer
because of a silly big request?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
These seem like reasonable defaults which will make geoserver installations more robust. +1.
Andrea Aime wrote:
About being stricter,
what do you think of locking down the WMS limits a little
bit by default for 2.0?
Not so much, something like:
- max wms request time: 1 minute?
- max memory used in a single request: 64MB?
- max error count: 1000Not too strict but should avoid people restarting GeoServer
because of a silly big request?Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
+1
Justin Deoliveira wrote:
These seem like reasonable defaults which will make geoserver installations more robust. +1.
Andrea Aime wrote:
About being stricter,
what do you think of locking down the WMS limits a little
bit by default for 2.0?
Not so much, something like:
- max wms request time: 1 minute?
- max memory used in a single request: 64MB?
- max error count: 1000Not too strict but should avoid people restarting GeoServer
because of a silly big request?Cheers
Andrea
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.