On Thu, Jun 2, 2011 at 5:32 AM, Gabriel Roldán <grol...@opengeo.org> wrote: > I'm up to implement this. Question is what would be preferable, a new > list property in WMSInfo for the blacklisted mime types, or just use the > WMSInfo's metadata map? > > Being something that goes in "core" wms I'd say the correct thing to do > is to roll over a new property. Opinions?
I would go core if you implement it only on trunk, metadata if you want to backport it to 2.1.x too. For time and elevation support I'm adding 8 new properties, all in the metadata exactly because I want to backport it to 2.1.x, where, _I believe_, changes in the config and xml serialization structure are not welcomed. I may be wrong. Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
