Hi, all!
Out of the long/divergent "Java" thread (which wasn't really about Java, it
turns out), a new capability has been born - we can now use files as POST
data for JSON mode. This takes us one step further towards removing some of
the minor arg-handling differences between CLI and HTTP modes...
[stephan@cheyenne:~/cvs/fossil/fossil-json]$ cat in.2
{
"requestId":"POST from file test",
"command": "timeline/wiki",
"indent":2,
"jsonp": "myJsonCallback",
"payload":{
"limit":1
}
}
[stephan@cheyenne:~/cvs/fossil/fossil-json]$ ./fossil json --json-input
in.2
myJsonCallback({
"fossil":"225fd3dad33e7a945d0ade473ab39cc5110c77b7",
"timestamp":1317560927,
"requestId":"POST from file test",
"procTimeMs":1,
"payload":{
"limit":1,
"timeline":[{
"rid":12811,
"uuid":"a7e68df71b95d35321b9d9aeec3c8068f991926c",
"timestamp":1310227825,
"comment":"Changes to wiki page [Apache On Windows XP]",
"user":"jeffrimko",
"eventType":"w"
}]
}
})
The infrastructure won't let us open a single fossil process to which we can
send multiple such commands (that would be a nice performance improvement,
though), but this should simplify the creation of script-based wrappers,
since they no longer have to know the difference between, e.g. CLI's
--indent and POST's "indent" options - they can simply set all options in
the POST data. (POST also has the advantage of keeping more type
information, whereas CLI/GET params are always strings.)
--
----- 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
