Justin Deoliveira wrote:
> Caching of the resoures is not so much the issue imho, rather than how 
> we access resources on startup. Currently on startup every datastore is 
> connected to and every feature type is loaded. It will take a bit of 
> work to make sure everything is loaded lazily.
>   
Reminds me; we originally were lazy and were forced to be greedy as 
requests would time out while waiting for ArcSDE (for example) to 
connect. Can we
have some kind of priority for that LRU queue; setting up an 
SeConnection is way more expensive then opening a shapefile; or even 80 
shapefiles.
> But part of the reason why isolating all resource access is nice is it 
> gives us one place to worry about resource loading. Which I think is the 
> first step toward coming up with something better than what we have today.
>   
jdeolive++

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

Reply via email to