diff options
| author | Bryan Newbold <bnewbold@robocracy.org> | 2017-10-25 00:17:53 -0700 |
|---|---|---|
| committer | Bryan Newbold <bnewbold@robocracy.org> | 2017-10-25 00:17:53 -0700 |
| commit | b7f5ff95f129e69c953b099bcad7febdf405d307 (patch) | |
| tree | 09afe6529960139a14d0b82fb5a28cadffc16db8 | |
| parent | bc973d25d1e44c34ee05c0a47639b7e352ddd5a9 (diff) | |
| download | geniza-b7f5ff95f129e69c953b099bcad7febdf405d307.tar.gz geniza-b7f5ff95f129e69c953b099bcad7febdf405d307.zip | |
spec notes update
| -rw-r--r-- | notes/spec_todo.txt | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/notes/spec_todo.txt b/notes/spec_todo.txt index ad05c69..9a953c4 100644 --- a/notes/spec_todo.txt +++ b/notes/spec_todo.txt @@ -10,6 +10,10 @@ Things that were underspecified in the spec/whitepaper: - "append only" is mentioned many times, but need to write "back in" to merkel tree on many occasions - inconsistent message names between .proto and whitepaper +- protocol extension stuff not in the whitepaper +- whitepaper should be versioned/tagged, or marked as "work in progress" +- encryption not really covered in whitepaper... seems to be XSalsa20 XOR'd + with data "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, @@ -18,7 +22,11 @@ node.js specific? "If you are sharing multiple hypercores on the same port you can use this event to wait for the remote peer to indicate which hypercore they are interested inj" - 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? + +varint-encoded message prefix for network messages still feels sort of +inefficient... fixed 32-bit length makes more sense to me, seems like +efficiency gains would be pretty small. would need benchmarking. + https://developers.google.com/protocol-buffers/docs/techniques#streaming |