Hubs-Foundation / Hubs-Foundation/dialog
New peer takes too long time to be notified
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
New peer notification on producer side takes too long after consumer is already receiving data. Is it possible to get this or another notification on producer side when the consumer receives the first data?
Consumer first receive data at 12:14:40
p.s.:("data sent at ..." is the content of the message received)
Producer receives new peer notification after almost 30 seconds
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Reproduce the producer and consumer timing described in the screenshots, then trace the existing new-peer notification path to determine when it fires relative to the consumer's first received data. Done means the producer receives an appropriate notification at, or acceptably close to, first data receipt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100