I am interested! And I've read the guidelines posted in one of the replies, but I'm also not sure how useful this might be for the community in general, at the moment (considering the replies meanwhile). I have no doubt that if a rest api already exists and have a logic behind each HTTP request, to make it actually do what is documented is the minimum one expects. Regarding databases, it could simply forbid operations but, at the moment, it does half the job by updating only xml metadata files and making geoserver incoherent with data itself (which, in consequence, makes the layer not usable anymore). As a workaround, as I control both frontend and backend, I was able to build a separate piece of software to do these updates on database, on request (alter and drop table, which were plain simple to make). What took a bit more time to do was related to user authentication. Nothing of this would be needed if put and delete behave properly on DB:)
-- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
