Jody Garnett wrote:
>
> I am not sure if this idea holds any appeal. It may be a bad product
> idea to introduce a REST API as a distinct layer; it would be way too
> easy make new functionality quickly via REST and forget to keep the web
> client up to date and in sync.
On the other hand...
1) It would put to test the soundness of the RESTful API (eat your own
dog-food).
2) It would allow the building of mapserver-appliances (GeoServer instances
without UI) useful in production environment.
3) It would reduce the footprint of GeoServer and decouple it from the
front-end baggage (be it Struts, Wicket, Cocoon, whatever).
4) It might even lessen the level of anxiety of Andrea ;) , who fears
reduced productivity when juggling with technologies other than Java
(just split the team in two: one taking care of "core" GeoServer, the
other of the UI).
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
