+1. Seems necessary, and the changes are not too intrusive. Kind regards, Ben.
On 21/03/17 05:09, Torben Barsballe wrote: > This was initially proposed just prior to the 2.11-beta release, but did > not make it in in time. > Re-opening for discussion and voting now that the code freeze has ended. > > Refer to https://github.com/geoserver/geoserver/wiki/GSIP-157 > > This proposal is to update the CatalogPostModifyEvent (and associated > firePostModifed methods) to track changed values, similar to the current > implementation of CatalogModifyEvent. > > This requires some API changes in a few catalog methods and interfaces. > > Ultimately, it is a useful, but relatively minor change requiring some > not-backwards-compatible API changes to the core catalog implementation. > > Full set of proposed changes can be seen in the pull request > <https://github.com/geoserver/geoserver/pull/2101>. > > Torben > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
