Justin Deoliveira ha scritto: ... >> I also hope we'll have a good storage granularity, that is, we'll have >> to try and make sure we just save what's strictly necessary, avoiding >> to store the whole catalog in a single shot, which may become an >> expensive operation when hundreds of feature types are configured. > Yeah... depends on how we do it. As you say if we serialize in one shot > it could lead to a huge file that needs to be read back in. Off the top > of my head what might work well is to keep the separation we have today > between the catalog.xml and individual info.xml files per feature type. > That coupled with lazy loading should lead to some good results.
I'm wondering if we really need to reload back in anything... modify the configuration model directly (in future) save the bit that needs to be saved, and be done with it? Reloading back in has the advantage of letting you know you're screwed... the very moment you are, instead of waiting for the next restart, so it may be a good debugging tool, but I'm wondering if it is necessary for normal operation. Again, I'm talking of phase 2, not the current proposal scope. >> Finally, is the resource pool maintained accordingly, >> that is, avoiding to drop and recreate all datastores like we do now, >> at great expense of time, especially for some datastores like SDE? >> At the same time it would be wise to remove datastores from the pool >> if removed from the configuratin, since some of the cached objects >> (connection pools) are scarce resources. > Unfortunately not as implemented currently. Having to maintain total > backwards compatibility with the UI has forced us to mimic the way > things work today. Yep, but when we get rid of it, we can be smarter and avoid reloading everything, right? ... > Interesting... I am not sure I quite understand the use case. Think of an application built on top of GeoServer that builds summarizing views of data for a specific user that then wants to see the data on the web with wms. To do so you have to configure a new layer, but at the same time, that layer is sort of private to that user, it's part of his conversation with the application. 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
