On Nov 21, 2015, at 3:50 PM, Tom Browder <tom.brow...@gmail.com> wrote:

> Can we choose (at least initially) a binary format to get started
> with?  From my brief look at the three:

Sure, and I think your summarization of pros/cons is spot on with what I’d 
gathered about them as well.  BSON is huge and well-tested simply because of 
Mongo.  The other two improve upon BSON but are not as mature, not as widely 
adopted.  Can you find users of the latter two?

I’m inclined to go with one of the latter two but have no gut feeling that any 
would be better for us than the other at this point.  BSON or UBJSON looks to 
be the easiest to try.  If there are serious projects using CBOR, and use it on 
Windows, that would be interesting … porting it to Windows for them doesn’t 
sound appealing.  Them being the only one standardized, though, does sound 
appealing.

Thoughts?  Your “caveat” at the end sounds like the best next step to me.

Cheers!
Sean
 

 
> 
> ===========
> 
> BSON
> ---------
> 
> + Apache 2 license
> + C implementation available (uses CMake, has extensive test suite), see:
>   https://github.com/mongodb/libbson/tree/master/
> + docs: use xml format
> + specification version 1, see:
>   http://bsonspec.org/spec.html
> + conversion to/from JSON: ???
> 
> + pros: assume it has lots of use with MongoDB
> 
> UBJSON
> -------------
> 
> + MIT license
> + C implementation (uses CMake, has small test suite), see:
>   https://github.com/Steve132/ubj
> + docs: limited
> + specification draft 12, see:
>   http://ubjson.org/
> + conversion to/from JSON: ???
> 
> + pros: simple code
> + cons: limited documentaion
> 
> CBOR
> ---------
> 
> + MIT license
> + C99 implementation available (uses CMake, has extensive test suite), see:
>   https://github.com/PJK/libcbor
> + docs: use rst format
> + stable specification (RFC 7049), see:
>   http://tools.ietf.org/html/rfc7049
> + conversion to/from JSON:
>   - non-normative recommendations in spec
>   - ???
> 
> + pros: RFC spec, C99 standard (expedite getting our source onboard
> with C99 or, better yet, C++)
> + cons: MSVC still has no support for C99 (let's move to C++!!)
> 
> ===========
> 
> All look usable as 'other' src.  I have not tried any implementations yet.
> 
> A caveat: we probably should check docs and conversions to/from JSON
> for each version (specification and implementation) which I have not
> yet done.
> 
> ...to be continued
> 
> Best,
> 
> -Tom
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel


------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to