libp2p / libp2p/go-libp2p-pubsub
Allow per-topic message size limits
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to be able to configure a maximum message size per topic. For example, filecoin transactions should never be larger than 32k, but block messages might be larger than that.
I don't want to have to read the entire object from the other peer into memory before i drop it, I should be able to detect the message is too big, and then either kill the connection, or discard the bytes as they come in.
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
The issue names no files or tests. Start by tracing the pubsub message receive path and how topics are configured; define where a per-topic limit can reject or discard oversized messages before the full object is buffered, then verify both connection-closing and byte-discarding behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100