ashrafee-dev / ashrafee-dev/scamshield-api
Refinement: WebSocket Binary Framing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 44m
- Merged PRs (30d)
- 9
Description
The current WebSocket loop assumes every receive_bytes() call is a complete, valid audio file. In real-world streaming, you may need to handle chunked binary data.
Task
Research and implement a basic header or framing logic if the client is intended to stream a single continuous audio feed rather than multiple small files.
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 tracing the WebSocket loop and its receive_bytes() calls, then determine whether the client sends one continuous audio feed or multiple files. Research the expected framing contract and document the cases the implementation must distinguish; done means chunked binary input is handled according to that contract without treating each receive as a complete audio file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, audio-video-rtc, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100