Justin Deoliveira wrote: >> Resource pool... wondering if we may be served better by a method >> like: >> >> catalog.getResourcePool().getResource(DataStore.class, this); >> >> and have that method backed by a set of pluggable resource loaders. >> The alternative is changing the ResourcePool API any time we need >> to cache a new kind of resource. Which may not happen that often, >> so it's a good alternative. Just wanted to present the options. >> > This is an interesting thought Andrea. Just thinking about people who > will want to write their own services which have special resources, like > say perhaps WPS. I like this idea... +1. > heh; now you are caught up to the major benifit of the uDig catalog. Also plus one; but you may want a getDataStore method to start out with just to be explicit (the major complaint we have with the udig catalog). > Still there, and it works like before since the *.config objects still > mirror the *.global objects. Once we remove the config layer then we > will be playing a direct access game. Is the direct access game (when it arrives) going to be confusing for us? ie do we need to think about events... Jody
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
