Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1231
> If you are expecting to code the entire DHT from scratch, it's too tough
for me
That is not an expectation here of course.
Let's think about alternatives - another way is to distribute note.jspn
though regular torrents, right? So we can assume that there is going to be a
tracker one day, that lists all notebook that are shared and each Zeppelin
instance will be just seeding it's own fraction of notebooks.
Then each revision of the note need to be stored as a separate file, as it
will create a new torrent file\magnet link, right?
Do you think this will work?
1. listing existing notes that shared through Bittorrent
This will include listing local copies from filesystem i.e under
`/notebook/bittorent` or `/notebook-bittorent` not to interfere \w existing
VFSNotebookRepo impl.
2. checkpointing AKA creating revisions
Each revision will result in a new file i.e `note-revisionId.json` + a
new .torrent/magnet link to share it
3. listing revisions for each note
This should be simple, given the assumptions from above. And each
revision can be shared independently
4. importing new note by magnet link (should work similar to current
"import by URL")
---
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.
---
