tuzig / tuzig/webexec

Break large buffers before sending

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue hacktoberfest
Dominant language
Go
Stars
38
Forks
3
PR merge metrics
No merged PRs in 30d

Description

WebRTC can handle messages up to 64K long and sometimes they are longer.
Today send receives and error and the data is never sent.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the WebRTC data-channel send path in this Go repository and inspect how oversized messages are handled. Verify the behavior with messages over 64K: they should be sent in smaller pieces instead of being lost after a send error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
audio-video-rtc
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.