Github user onkarshedge commented on the issue:
https://github.com/apache/zeppelin/pull/1231
@bzz I read the [DHT
specification](http://bittorrent.org/beps/bep_0044.html) and here are some
questions and answers.
Answer to point 2) checkpointing and 3) get Revisions
Mutable items can be stored with help of public and private key.
`dht.mput(publicKey, privateKey, new Entry(data));` and retrieved via
`dht.mget(publicKey)`. This allows only to store only one item/note against
your public key. On retrieval the latest revision is retrieved, highest `seq`
number. We can store multiple notes also if we use `salt`, the key in DHT would
be hash(publicKey+salt), the salt could be `noteId`. But still we can only get
only latest revision as per the protocol.
If we use Immutable items to be stored in DHT `dht.put(data)` returns SHA
hash and we can get the item back from DHT via ` dht.get(hash)`. So we can keep
track of all revisions by storing hash against the noteID. `noteID -> [hash of
rev1,hash of rev2]` in some Map\<String,List\<String\>> .
point 4) Magnet Link.
magnet link are used to receive the metadata(info) of the .torrent
file.Once the metadata part is received it downloads the file. In order for the
peer to receive the file it needs seeders. Why use magnet link to import ? as
we are storing notes directly in DHT we can just use hash(returned from
dht.put("data") ) to get it from DHT.
point 1) Listing existing notes
will this be VFSNotebookRepo's list() method ? I didn't get this one.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
