Messages should be idempotent or recognizable as duplicates
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I just noticed this in the [RFC](https://tools.ietf.org/html/rfc7574#section-8.2). Messages can be resent and the receiver has to be able to deal with that gracefully.
> All messages are idempotent or recognizable as duplicates. Idempotent means that processing a message more than once does not lead to a different state from if it was processed just once. In particular, a peer MAY resend DATA, ACK, HAVE, INTEGRITY, PEX_*, SIGNED_INTEGRITY, REQUEST, CANCEL, CHOKE, and UNCHOKE messages without problems when loss is suspected. When a peer resends a HANDSHAKE message, it can be recognized as duplicate by the receiver, because it already recorded the first connection attempt, and be dealt with.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 7574 section 8.2 and tracing how the Go implementation handles DATA, ACK, HAVE, INTEGRITY, PEX_*, SIGNED_INTEGRITY, REQUEST, CANCEL, CHOKE, UNCHOKE, and HANDSHAKE messages. Define how repeated messages should preserve state or be recognized as duplicates, then verify each listed message follows that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100