Hey folks,
I wanted to run some proposed refactoring of the ResourcePool class past
everyone. Basically my goal is two-fold. The first and primary goal is to
extend to the jdbcconfig module to allow for storing SLD contents along
with configured style objects. It is really the last step to make the
module able to store all catalog contents in the database.
The idea would be to make it possible to plug in a custom ResourcePool
implementation via spring. The lookup mechanism is similar to how others
work in that first we would look for an instance in the spring context, and
if not found fall back to the default implementation.
A secondary goal is to allow for implementations to control how the various
caches in ResourcePool are created. One thing I have been wanting to
experiment with is the idea of distributed caches that GeoServers in a
cluster could potentially share. This secondary goal is not an immediate
one but I figured since i was mucking around in the vicinity i would make
these changes as well.
All in all the changes are pretty straight forward, and mostly a pure
refactoring with no behavioural changes.
https://github.com/jdeolive/geoserver/commit/2dd214507cd764486707ed93711f380ff4db0f71
Thoughts or opinions? Do people feel this is something proposal worthy? I
should note that i was hoping to do this on 2.3.x.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
