On Fri, Nov 4, 2011 at 7:48 PM, Alek Paunov <a...@declera.com> wrote:
> As Fossil API, for the proof of the concept, the server can use the JSON
> API, Stephan ?
>
>
The biggest catch there is binary data, since JSON has no native way of
handing it. However, my current thinking on binary data is this...
from JSON we serve URL paths which, which called by an HTTP client, will
return the raw content (binary or not) for the given artifact. We could
handle POSTed data the same way, _theoretically_. There is a bit of
proof-of-concept for that in the current timeline output:
...
"files":[{
"name":"src/json_user.c",
"uuid":"d860ffd974654d397cf3be9a39ec1eb99ea472b2",
"prevUuid":"4b9322d63bad1b18bb3fd24e435277fc852db7d6",
"state":"modified",
"downloadPath":"/raw/src/json_user.c?name=d860ffd974654d397cf3be9a39ec1eb99ea472b2"
}]
--
----- 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
