Jody Garnett ha scritto: > I was going over the documentation on the rest module; and trying to see > if it represented a stable picture of geoserver's configuration. > It appears I am missing some information in order to undertand what is > presented.
Jody, the problem I'm seeing here is that you're trying to comment on too much at the same time. One thing is the technical means we're using to present the configuration, and the other is the configuration itself. The two are in fact tightly connected, as the REST api is a pure reflection of the catalog API of GeoServer, but we cannot work on both of them at the same time, especially not on 1.7.x where the catalog API is mostly frozen. To handle the kind of structural changes you seem demanding for, we need to work on trunk and change the catalog api accordingly, and we need some funding to make the changes, or someone that wants to spend his time working on it. The topic of GSIP 33 is "is this REST api good to deal with the GeoServer catalog we have today?", what you're trying to discuss is "is the catalog API good for the next 5 years?" which is definitely a interesting topic, but a different one. Let's talk about it, but in a different thread, and then let's put the result, along with an estimation, on the roadmap ideas, and see if anyone is up to funding it. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
