Gabriel Roldán created GEOS-5010:
------------------------------------
Summary: Make GWC requests go through the GeoServer Dispatcher so they can be throttled by the control-flow module
Key: GEOS-5010
URL: https://jira.codehaus.org/browse/GEOS-5010
Project: GeoServer
Issue Type: New Feature
Components: GWC
Affects Versions: 2.2.x
Reporter: Gabriel Roldán
Assignee: Gabriel Roldán
Fix For: 2.2.x
All GeoWebCache requests other than "direct WMS integration" ones go through the GWC dispatcher, which is similar in spirit than the GeoServer OWS Dispatcher (but simpler).
This means GWC requests can't be throttled by the control-flow module.
Make it so that integrated GWC requests get handled by the GeoServer OWS Dispatcher, and hence they automatically engage into the control-flow module.
A mediator "gwc" service will be configured in the spring context, so that controlflow.properties can have a setting like:
{code}
ows.gwc=100
{code}
There will be a single "fake" operation in this service, named "dispatch", as it doesn't make sense to be able of setting different control flow limits for the different tile services. It's just more convenient to be able of setting a throttling limit for all gwc tile requests, regardless of whether the request is a WMC-C, TMS, or WMTS one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira