On Thu, Oct 6, 2011 at 9:04 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> There are some (a small few) features which we can't provide over JSON > without some major workarounds and/or caveats. Namely binary data (which > JSON cannot natively support), which means committing binary files this way > will not be implemented, at least initially, and will have some significant > limitations if it is ever implemented (e.g. the RAM cost of committing > base64-encoded binary content in JSON form would be roughly 2-3x the > original content size, so it would likely fail miserably for those people > who think that having files >500MB in their repo is somehow a good idea). > > Hi Stephan, Do you know about "protocol buffers". I'm asking because I didn't know about them since recently. http://google-opensource.blogspot.com/2008/07/protocol-buffers-googles-data.html Could this help in order to allow binaries and improve the serialization performance? --Erlis
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
