Hi Geoserver community,
For every WMS layer that has latLongBoundingBox set up in the config, GeoServer
may restrict the request to the configured latLongBoundingBox. At the moment,
it doesn't, and this results in unnecessary query and wastes connections and
cursors (for Oracle).
Thus I propose to add an option in the code for latLongBoundingBox range
checking. the option will allow to filter the none result query which is out of
latLongBoundingBox range and improve the performance.
If community reckon that it is the right way, I am willing to submit a code
patch to implement it if necessary.
Thanks first,
Lingbo
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
