> > >> The api is going to undoubtedly change as we continue to change the > configuration. I have tried to hit a middle ground with the current rest api > that hits some of the concepts that we anticipate, 1) it groups by > workspace, not namespace, and 2) makes layer a separate entity when in > reality it is not, etc.. Versioning the api makes a lot of sense to me. And > when it does come to change I don't anticipate any issues with going though > a normal deprecation cycle first.
Thanks Justin this hits everything I wanted to know; we have some idea that the API will change and we have a way to communicate these changes to external applications. I am sorry I distracted the thread with ways I suspect the API will change - I was only doing so to explore if we could fit those changes into the current layout of the REST api. Thanks for talking this through with me; I feel it would of been easier if I had tracked the progress of this community module more closely. Jody
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
