Hi, everybody. I'm trying to use GeoServer in an instance where we have thousands of layers to register, with tens to hundreds of new layers each day. It seemed a perfect situation for dbconfig, but I'm having a lot of difficulty getting that module to work.
This can't be all that unusual a use case, though; does anyone here have any suggestions for strategies to make GeoServer scale better so that keeping the catalog around in memory doesn't become too onerous, and loading from disk if the webapp has to be reset doesn't take forever? Thanks in advance for any advice you can offer. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
