haskell-distributed / haskell-distributed/distributed-process
Support message fragmentation
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
Messages sent by Cloud Haskell processes are always sent whole, independent of their size. This means that when a process sends a very large message, it can hog the network connection (moreover, Network.Socket.Bytestring can't handle large messages).
See comment at https://github.com/haskell/network/issues/58#issuecomment-8929906 -- number of chunks passed to sendMany should be short (<= 16).
Contributor guide
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 tracing how Cloud Haskell processes send messages and where chunks are passed to sendMany; review the linked Network.Socket.Bytestring issue for the large-message constraint. Done means very large messages are fragmented so no sendMany call receives more than 16 chunks, while ordinary messages continue to send correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- 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