search

go-ndn / persist

NDN persistent content store
GNU General Public License v2.0
0 stars 1 forks source link

ipfs #2

Open joeblew99 opened 7 years ago

joeblew99 commented 7 years ago

its seems to me that IPFS can also be a good match.

It has a merkle tree and so your OT (operation Transforms) can be expressed within the merkle tree of IPFS easily. That essentially gives you the ability to hold OT's in order to do complex convergence apps like google docs.

NDN then is able to provide all the other stuff that it does.

what do you think ?

taylorchu commented 7 years ago

This package is meant to be a fast disk-based NDN cache store.

How do you plan to add ipfs in? Thanks!

joeblew99 commented 7 years ago

thanks. I think i can add IPFS by using a driver interface. In terms of architecture i am not sure yet. IPFS distributes the data between other nodes in a very very different way than NDN, but i see the two as having some complimentary properties. I am still playing around with both to be honest to see where the dovetail works...

joeblew99 commented 7 years ago

thanks. I think i can add IPFS by using a driver interface. In terms of architecture i am not sure yet. IPFS distributes the data between other nodes in a very very different way than NDN, but i see the two as having some complimentary properties. I am still playing around with both to be honest to see where the dovetail works...

Also my other concern is an event source pattern for apps to use NDN. I am using this with a boltDB with great results so far. It handle network partitioning well. Thinking about a golang port. https://github.com/y-js/yjs