livepeer / livepeer/go-livepeer-basicnet
TranscodeSub + Direct Connections
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Tracking issue for the proposal outlined in https://github.com/livepeer/go-livepeer-basicnet/issues/21#issuecomment-369310870
* [x] On-chain tracking of new jobs and assignments in transcoder.
* [x] Transcoder prepares to receive a direct connection (set up listeners if needed)
* [x] Transcoder sends `TranscoderSub(T_MultiAddr, T_NodeID, StrmID, T_Sig)` if assigned a job
* [x] Broadcaster handling for `TranscoderSub` request ; establish a direct connection
* [x] Transcoder handling of direct connection; SUB to broadcaster
* [x] Broadcaster handling of incoming SUB requests via the direct connection
* [ ] Verify TranscodeSub messages on broadcaster. Requires https://github.com/livepeer/go-livepeer-basicnet/issues/31 or monitoring the event log.
* [x] relay fallback (eg, if transcoder is NAT'd)
* [x] retransmissions for broadcaster misses
* [x] ~~disconnect handling~~
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 with the proposal in issue 21, then review issue 31 or the event log path mentioned in the remaining checklist item. Done means verifying TranscodeSub messages on the broadcaster; the issue does not name source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- audio-video-rtc, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100