coot
coot
That's up to the consensus to decide if they want to maintain CDDL specs - so I'll let @dnadales decide, but at least document the serialisation format for things that...
A slightly better approach is to just download block bodies in `block-fetch` protocol, right now we are duplicating downloading `headers` which we already know from `chain-sync`.
oh, that's what Edsko mentioned in the title :grin:
@njd42 if `block-fetch` just downloads block bodies (since headers we already have), we will still know who offered the block first. It's not not just about optimising when the network...
It's something we should validte, it's hard to judge how much negative impact this will have when a node is synced; but it will save bandwidth when a node is...
This actually can refer to two places `Network.TypedProtocols.Channel` and `Network.Mux.Channel`.
I think this has the same problem as `Collect`: it allows you to peek the value in the resond queue, but does not allow to do `orElse` on the queue...
And one problem hides in `blah`s :D, when one gets a `c` we need to continue with `Peer` that has one pipelined message less (we track it `PeerSender` type), so...
@turion free-algebras-1.2 is availble from hackage: https://hackage.haskell.org/package/free-algebras
I think we resolved the issue on slack, please re-open if it's not the case.