You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BITSWAP.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,9 @@ Bitswap is a data exchange protocol for sending and receiving content addressed
27
27
28
28
## Introduction
29
29
30
-
Bitswap is a message-based protocol, as opposed to request-response. All messages contain wantlists, and/or blocks. Upon receiving a wantlist, a Bitswap server should eventually process and respond to the requester with either information about the block or the block itself. Upon receiving blocks, the client should send a `Cancel` notification to peers that have asked for the data, signifying that the client no longer wants the block.
30
+
Bitswap is a message-based protocol, as opposed to request-response. All messages contain wantlists, and/or blocks.
31
+
Upon receiving a wantlist, a Bitswap server should eventually process and respond to the requester with either information about the block or the block itself.
32
+
Upon receiving blocks, the client should send a `Cancel` notification to peers that have asked for the data, signifying that the client no longer wants the block.
31
33
32
34
Bitswap aims to be a simple protocol, so that implementations can balance aspects such as throughput, latency, fairness, memory usage, etc. for their specific requirements.
33
35
@@ -88,7 +90,7 @@ message Message {
88
90
89
91
All protocol messages sent over a stream are prefixed with the message length in
90
92
bytes, encoded as an unsigned variable length integer as defined by the
0 commit comments