Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi Andrea,
I think you misinterpreted my comments :). I was not saying that we
should not ship a UI in favor of a REST api, I was simply saying that
with a good REST api, the UI becomes less of a necessity.
I understood that. I'm just thinking the UI as a necessity and the
REST api as a nice to have (in my mind the first is what makes you
want to try out GeoServer, whilst the latter is something needed
for advanced usage only).
Sorry, I missed this before I wrote my email. From my perspective a
REST configuration API is just about required. It's great for advanced
users, and is great for javascript hooks to experiment with other UIs,
as well as to script configuration from other languages. To be a modern
internet application I'd say it's just about required. I'd be open to
pushing on it just after we finish the UI up, or to do it in
conjunction, but it's not something I want to wait much longer on. And
we have been making good progress on it already.
best regards,
Chris
begin:vcard
fn:Chris Holmes
n:Holmes;Chris
org:The Open Planning Project
adr:;;349 W. 12th Street, #3;New York;NY;10014;USA
email;internet:[EMAIL PROTECTED]
title:Managing Director, Strategic Development
x-mozilla-html:FALSE
url:http://topp.openplans.org
version:2.1
end:vcard
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
