Commit 5e08a77
committed
blockservice: move to single unique struct and add
The idea is to have a THE blockservice object, this means we wont ever have an issue where multiple competitive features play poorly with each other due to how nested blockservices could do.
Let's say we add multi-exchange based on content routing, do we want to have to handle the mess this could create with nested blockservices ?
It implements features for ipfs-shipyard/nopfs#34.WithContentBlocker option1 parent b8ac21b commit 5e08a77
File tree
8 files changed
+182
-111
lines changed- blockservice
- test
- fetcher/impl/blockservice
- gateway
- ipld/merkledag
- test
8 files changed
+182
-111
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
| 20 | + | |
20 | 21 | | |
21 | 22 | | |
22 | 23 | | |
| |||
0 commit comments