> > As far as I remember in the REST world one tends to "version" the > api and try to keep at least one old version around, not sure what > Justin's plan are on this one thought.
That sounds like a good approach. What makes people react negatively to your suggestion is that they > come with request of more work and no contribution on your part. I understand that - I tried to outline some integration options that would not disturb the existing rest layout but that was lost in the noise. The idea is welcomed, but the way you're expressing it seems like > twisting people arm into doing more work than they have resources for... > not surprisingly you get negative reactions. Okay to be clear: - I expect no more work at a coding level - I expect us to either have an idea on how to extend the REST API without breaking scripts - or to have an alternative (such as making a new version of the API available) This is a massive increase in functionality; that exposes a lot more surface area of geoserver to other projects - as such this is a more serious contribution then any Java api changes - it really increases the expense for us to maintainer the application. It does offer massive benefits. This is my first serious review of the API being presented and I am trying to treat it with all the respect it deserves. This is a test of the process for merging in a community module is it not? And thus my first chance to review. Or if we do I would like to know that - and be up front with script writers >> that they will need to adjust their scripts to work with GeoServer 2.0. >> > > That is certainly a concern I share. This is becoming published api, > meaning that if we change it, we need to provide a migration path. Possibly > going thru intermediate deprecations and replacements. If you can tell me more about how a REST API is versioned that would close off this thread for me. I have already voted +1 on this matter; I feel like I am as much explaining myself as explaining my feedback. I would be happy to add information about REST API version to the proposal myself; if that is a sensible contribution. Jody
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
