-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Ipns Consistency #296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ipns Consistency #296
Conversation
@@ -1,6 +1,6 @@ | |||
{ | |||
"ImportPath": "github.com/jbenet/go-ipfs", | |||
"GoVersion": "go1.3", | |||
"GoVersion": "devel +9340f9f6dfc9 Fri Oct 31 00:48:57 2014 -0300", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
Great PR, as always. A few codebase-friendliness comments up there, but all this LGTM! |
5cfe20a
to
9301e61
Compare
@jbenet am i good to merge? |
@whyrusleeping depends, did the commands merge change anything here? we've officially deprecated |
If you merged over the ipfs name code then no, nothing should have changed. |
?? |
I mean, if you've ported over the code for |
those have been ported |
I'm going to rebase this on top of new master first. |
test(time) expose time format var License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
When a peer is found, add its addr to the peerstore, just like the addresses for closer peers are added. In particular this is helpful for followup queries by the DHT user.
This PR changes the DHT so that it stores records instead of simple values. This allows us to add a layer of security onto the DHT, and also allows us to validate values that are stored in it.
Currently, only two value types are allows to be stored in the DHT:
Other types of Ipns Validity functions should be discussed, as only one is implemented. More complex checks may require a change in how the validity functions are called (maybe add new parameters, etc).