Hey what do people think about making RESTConfig a default part of GeoServer for the 2.1.x release? I think it's one of the most popular modules, and could be helpful if people didn't have to install it. Checking the stats it edges out Oracle for the most popular in both 2.0.1 and 2.0.2.
I think the one thing we need to do to bring it in to core is actual version the API. Putting it in core means we should commit to the API, and not break clients at all if we want to make incompatible changes. See http://barelyenough.org/blog/2008/05/versioning-rest-web-services/ http://stackoverflow.com/questions/389169/best-practices-for-api-versioning http://resources.esri.com/help/9.3/arcgisserver/apis/rest/versioning.html It seems like most people are pretty happy with the current API, but we should do some searching of feedback and get another round, to make sure it's an API we feel good about. Chris ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
