> Maybe you could do some http-over-stdin/stdout, and speak json there. :)
Isn't "fossil cgi" already doing that? A front-end could build the appropriate environment variables and fork/exec "fossil cgi", feeding the post body to fossil's stdin. Actually, I was thinking that http/json was a more modern and universal API for doing a fossil lib than an API based on a long list of C functions and structs. > after every command fossil runs, exit() is called somewhere, which makes it > difficult or impossible to chain commands together in the same app session. Why? Paul On 1 Oct 2011, at 13:42 , Stephan Beal wrote: > 2011/10/1 Lluís Batlle i Rossell <virik...@gmail.com> > Maybe you could do some http-over-stdin/stdout, and speak json there. :) > > I think of people wanting to write frontends to fossil. > > i was just thinking about that while i was out shopping. It is, in principal, > possible, but fossil's heavy use of exit() as an error recovery strategy > would interfere with that. After every command fossil runs, exit() is called > somewhere, which makes it difficult or impossible to chain commands together > in the same app session. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
