[Noisebridge-discuss] File format specification

[Jeff Tchang]

Just want to chime in that as far as data interchange formats go JSON
makes me feel happy.

It is stupid simple and tends to be widely support with lots of
libraries. Binary data can be hex or base64 encoded.

For me when I see a good JSON object I hardly even need to look at the
specification. It's pretty clear what is what.

-Jeff

On Fri, Mar 19, 2010 at 9:16 AM, Bryan Beeley <bryan at beeley.org> wrote:
> It may be worth taking a look at M's JSON (or mjson).  I looked at both
> json-c and mjson for a project I started back in September and decided on
> mjson.  Unfortunately I don't remember the reasoning behind my decision, but
> I can say that I was pretty happy in using it.
>
> http://sourceforge.net/projects/mjson/
>
> Bryan
>
> Jacob Appelbaum wrote:
>
> John Menerick wrote:
>
>
> http://oss.metaparadigm.com/json-c/
>
>
>
> I found that url as well. It looks reasonable in a mere 333K. The
> license appears compatible too. Yay for Free Software!
>
>
>
> Looking through google code search for one of the header file names
> ->
> http://www.google.com/codesearch?q=json_util.h&hl=en&btnG=Search+Code
> shows there are a few programs using this library
>
>
> I'll take a look at it. It seems pretty much like it should fit all of
> my needs.
>
> Thanks guys!
>
> Best,
> Jake
>
>
>
>
> ________________________________
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>
>
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>
>