I would very much like to see the property data store retained in its current form. In addition to being exceptionally useful for pedagogical purposes, I can imagine intermediate-level users adding a one-point or two-point layer with some markers to a map, some bit of static data that is not handy in a database but they would like to serve to improve their maps. I can imagine little python scripts creating property files. Sure these things can grow to inefficient proportions, but just because a tool can be misused does not mean we should take it away.
It should be documented. We have made a lot of use of property file data stores, so I am in a position to document them. If you agree to keep it I will document it. -- Ben Caradoc-Davies <[email protected]> Software Engineer, CSIRO Exploration and Mining Australian Resources Research Centre 26 Dick Perry Ave, Kensington WA 6151, Australia ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
