-
Intro #10 and #12 issues.
Adoption of anytype flat container aka array.
Proposal: adding to spec new type of container.
```
< - open chevron - start of container
> - close chevron - end of containe…
-
When UBJSON spec was originally defined, all containers had a length prefix, like:
```
[A][5][...5 things...]
[O][2][...2 things...]
```
Part of the work in Draft 9 was to go away with the concept o…
ghost updated
10 years ago
-
Based on the results in #9, I recognize that BSON is actually very inefficient for arrays.
I researched this and looked at BJSON, UBJSON, Protocol Buffers, Thrift and Smile before finally deciding th…
-
From the documentation, it's unclear how a parser is supposed to determine the difference between a 1 and 4 byte length type. The documentation states that valid ranges for 1-byte values are 0..254.
…
-
Wanted to know what you guys thought...
Given the JSON Array:
[ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 ]
The current UBJSON is:
[[]
[i][0]
[i][1]
[i][2]
[i][3]
[i][4]
[i][5]
[i…
ghost updated
11 years ago
-
A popular pattern for embedding binary objects in JSON is to store their value as a Base64 encoded String according to:
http://tools.ietf.org/html/rfc4648#section-4
What I propose here is an optimiz…
ghost updated
11 years ago
-
'huge' would appear to be a base-10 representation of the number as a string.
Being awkward, I might prefer base-36 because it is more compact and thereby produce a spec-compliant but incompatible im…
-
JSON does not support special quantities (+/-infinity and the various versions of NaN), and therefore requires them to be represented as null. I suppose that this decision was made to avoid introducin…
-
This is something I have been thinking about, direct support for a "compressed" container that indicates the payload inside is compressed with GZip (assuming most common and well support algorithm)
[…
ghost updated
11 years ago
-
For example:
```
[o][255]
[B][1][b][2]
[B][2][b][4]
[B][3][b][6]
[B][4][E]
```