> > I still feel a pool managed by geoserver with multiple regions is a > better solution. That ensures SDE gets its own queue, so that nobody > will kick it out of it, and allows GeoServer to get rid of the > connection and its pool when the user removes the datastore.
Yeah I like this idea of grouping resources into "levels" based on how expensive they are to create / destroy. You said before that it would be nice to have an extension point bases system for resources. So I imagine at point there will be some sort of "ResourceFactory". I can see adding a method like: int getLevel(Object) Which would rate the resource in terms of its cost and it could be grouped accordingly. Just a thought. > > Cheers > Andrea > > !DSPAM:4007,4836ddce204428992556831! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- 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
