On 04.11.2011 21:01, Stephan Beal wrote:
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:
This approach (binaries via URL "pointers" on get/direct POST payloads
on send) seems OK to me ...
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
