> On 14 Oct 2017, at 21:23, Kristian Thy <[email protected]> wrote: > > On Fri, Oct 13, Jason Newmoyer wrote: >> As far as validation, I would look to do as much as possible from the >> client side. Even if that means calling a simple web service that you >> provide yourself that can respond with yes/no and error message. It usually >> results in a better UX this way. > > While client side validation is nice for the UX, server side validation > is obviously indispensible prior to a data update. > > Depending on how expensive validation is, you can then consider making > it available as a web service that you can _also_ call from the client. > > /Kristian
After some thinking about it, I'm considering to separate out the augmentation & validation tasks, and call both from the frontend for immediate validation/modification, and only the validation as part of intercepting the geoserver request/transaction. That should avoid the need for anything apart from aborting the transaction in the tx hook, which I can already do with the scripting plugin or possibly a custom extension. I'm still interested in what might be involved in a 'proper' TransactionPlugin that can modify content, since under some conditions I may not control the clients enough to force them to do the modifications themselves. That's hopefully further down the line though. Cheers, Tom ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
