use a third-party pubsub library for internal communications Insights: * Within bitswap, the actors don't need anything more than simple pubsub behavior. Wrapping and unwrapping messages proves unneccessary. Changes: * Simplifies the interface for both actors calling GetBlock and actors receiving blocks on the network * Leverages a well-tested third-party pubsub library Design Goals: * reduce complexity * extract implementation details (wrapping and unwrapping data, etc) from bitswap and let bitswap focus on composition of core algorithms operations
| 名称 |
最后提交
|
最后更新 |
|---|---|---|
| .. | ||
| bitswap.go | 正在载入提交数据... | |
| ledger.go | 正在载入提交数据... | |
| ledger_test.go | 正在载入提交数据... | |
| message.go | 正在载入提交数据... | |
| message.pb.go | 正在载入提交数据... | |
| message.proto | 正在载入提交数据... | |
| message_test.go | 正在载入提交数据... | |
| notifications.go | 正在载入提交数据... | |
| notifications_test.go | 正在载入提交数据... | |
| strategy.go | 正在载入提交数据... | |
| strategy_test.go | 正在载入提交数据... |