aboutsummaryrefslogtreecommitdiffstats
path: root/notes/spec_todo.txt
blob: b361f709c99ca5d814ecc186482e59ce3f5f8baa (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

Things that were underspecified in the spec/whitepaper:

- endianness of magic (big-endian)
- uppercase/lowercase of algorithm name (inconsistent in one place)
- what if there is only a single chunk/entry in a register tree? then a leaf
  acts as a root?

"You can use the byteOffset property in the Stat meta- data object to seek into
the right position in the content for the start of this chunk." => unnecessary,
node.js specific?

Clarify: appending to tree SLEEP results in writes into middle of file (for
root nodes). This seems not-great for performance (can't bulk-write). Better to
cache or work in RAM then batch commit?