-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Some Bitswap Refactoring #140
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,13 +8,24 @@ import ( | |
u "github.com/jbenet/go-ipfs/util" | ||
) | ||
|
||
type strategist struct { | ||
ledgerMap | ||
strategyFunc | ||
} | ||
|
||
// LedgerMap lists Ledgers by their Partner key. | ||
type ledgerMap map[peerKey]*ledger | ||
|
||
// FIXME share this externally | ||
type peerKey u.Key | ||
|
||
// TODO declare thread-safe datastore | ||
// TODO niceness should be on a per-peer basis. Use-case: Certain peers are | ||
// "trusted" and/or controlled by a single human user. The user may want for | ||
// these peers to exchange data freely | ||
func New(nice bool) Strategy { | ||
func New(trusted bool) Strategy { | ||
var stratFunc strategyFunc | ||
if nice { | ||
if trusted { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is misleading... trust has a very specific meaning in distributed systems. And this is not it. While this variable name choice is quite arbitrary, "niceness" is better and "trust" is misleading, so this change won't make it in. |
||
stratFunc = yesManStrategy | ||
} else { | ||
stratFunc = standardStrategy | ||
|
@@ -25,17 +36,6 @@ func New(nice bool) Strategy { | |
} | ||
} | ||
|
||
type strategist struct { | ||
ledgerMap | ||
strategyFunc | ||
} | ||
|
||
// LedgerMap lists Ledgers by their Partner key. | ||
type ledgerMap map[peerKey]*ledger | ||
|
||
// FIXME share this externally | ||
type peerKey u.Key | ||
|
||
// Peers returns a list of peers | ||
func (s *strategist) Peers() []*peer.Peer { | ||
response := make([]*peer.Peer, 0) | ||
|
@@ -89,7 +89,6 @@ func (s *strategist) MessageSent(p *peer.Peer, m bsmsg.BitSwapMessage) error { | |
for _, block := range m.Blocks() { | ||
l.SentBytes(len(block.Data)) | ||
} | ||
|
||
// TODO remove these blocks from peer's want list | ||
|
||
return nil | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
the rand object we instantiate should be stored somewhere, possibily in the ledger. and should be constructed when the ledger is created.
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.
Also, the seed should be seeded by time, (or a random number from crypto/rand)
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.
@llSourcell ... why did you introduce a constant seed? This is wrong.
rand.Float64
will draw from the default source, which we can initialize with a random seed usingrand.Seed
.