Jody Garnett ha scritto: > 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.
Ah ha, interesting one. LRU already has its own priority (you get to top when used and move towards the land of the dead when others are used), wouldn't adding another priority concept mess up things? What about having multiple queue, and a way to set a "regionId" or something like that to decide in which queue a resource ends up? Most datastores may end up in the standard ds queue, but some, like ArcSDE, and maybe WFS and Oracle (when not using JNDI pools) should end up in their own? Cheers Andrea ------------------------------------------------------------------------- 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
