On Fri, Aug 17, 2012 at 7:03 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Sat, Aug 18, 2012 at 1:31 AM, Miles Fidelman <mfidel...@meetinghouse.net> > wrote: >> Is there any kind of RESTful API for accessing Fossil repositories? > > https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/view
That's very nice. Thanks! > That's about the closest thing there is. It's not REST, but it's REST-ish > (JSON-over-(HTTP-or-file). What's not RESTful about it? At first glance I see it uses GET and POST appropriately, not using GET to create things, using POST to create/modify things. It doesn't use DELETE, but then that's because Fossil deletes nothing, right? As for PUT... POST for creating resources seems to be more popular now. That leaves the non-use of HTTP status codes, IIUC. But I do think that HTTP status codes should be used, and it's OK to deliver more application-specific status codes in the response entity. Nico -- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
