Hi,

I recall that (b)geo are now base on JSON.

I also recall a mentioned about binary JSON work by Side Effects.

Is the binary JSON work push back to BSON or other standards body/open-source projects ?

Cheers

nicholas_yue
Hi,

I recall that (b)geo are now base on JSON.

I also recall a mentioned about binary JSON work by Side Effects.

Is the binary JSON work push back to BSON or other standards body/open-source projects ?

Cheers

BSON wasn't around when we created our implementation of binary JSON. Neither were some of the other binary json formats that are kicking around now.

Our implementation is much simpler in many respects (i.e. we don't have elements for date/time or javascript code). However, our implementation is different in that:
a) We support fpreal16 storage
b) We support efficient encoding of uniform arrays of uniform data.
c) We have support for storing string tokens to reduce storage for common string values (similar to the smile format)

Our implementation is actually closer to http://bjson.org/ [bjson.org] than it is to BSON.

You can inspect our implementation looking at $HH/public/binary_json.

As a note, our encoding for the examples on the BSON page would be:

{“hello”, “world”} -> “\x7fNSJb{+\x00\x05hello&\x00+\x01\x05world&\x01}”

{“BSON”: } -> "\x7fNSJb{+\x00\x04BSON&\x00}"

As a note, with the header (5 bytes), the first example encodes to 27 bytes, the second to 42. The BSON examples are 22 bytes and 49 bytes respectively.

Hi Mark,

Is there any chance of sharing a C++ module for SESI's implementation of Binary JSON? I'd like to write bgeo's from C++, too .

Thanks,
Jason

jason_iversen
Hi Mark,

Is there any chance of sharing a C++ module for SESI's implementation of Binary JSON? I'd like to write bgeo's from C++, too .

Thanks,
Jason

You can use UT_JSONWriter/UT_JSONParser. I don't believe that these incur a license hit at the current time.

Ah, thanks Mark! I'll give it a whirl.