On 09/08/11 16:01, Stephan Beal wrote:
Hi, all!
Management Summary: if you are _at all_ interested in seeing a JSON
REST-style interface added to fossil, please continue reading. If not,
don't bother!
Since you've read this far, we'll go ahead and continue...
Earlier this week i was awarded the great pleasure of sitting down with
DRH himself for dinner in downtown Munich, Germany on what was
coincidentally the absolute nicest day we've had this whole summer. At
one point Richard asked me, "what does Fossil need?" To which i answered:
1) A split between library and app. i.e. libfossil vs. the fossil
server/cgi/shell app(s)
I couldn't agree more. One of my goals (luckily no milestone I'll ever be
evaluated against) is to do that.
2) A JSON interface.
I agree with the REST interface, choosing JSON seems natural, then. But then
again, you only need the JSON for the replies, not the requests themselves, as
the URL will contain the query (update, drop, ...) already. In case you have
data to accompany the request, I'm not sure that JSON is the right choice (in
contrast to multipart/forms), but I don't have a strong opinion on that one.
That being said, what about the CLI? If you're using client-side UI, then the
CLI should do that, too, shouldn't it? May I point to the wonderful jansson C
library (even though it's maybe too late already?), an easy to use,
lightweight, BSD licensed json library while we're at it.
Or is the CLI still going to be a "special case" ?
Anyways, thumbs up!
-Martin
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
