livepeer / livepeer/go-livepeer
Define "WebSocket" Orchestrator Capability
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Let's use Capability_WSTransport for the name.
Capabilities are defined in https://github.com/livepeer/go-livepeer/blob/249d9ebd80380dddd594e32bc9f44288d8b6fc33/core/capabilities.go
This property should initially always return "false".
Once @AlexKordic's work on websocket streaming is comeplete, we'll conditionally invoke it based on this property and cut a release with this capability always set to true.
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 in core/capabilities.go and review how existing capabilities are defined. Add the Capability_WSTransport property with an initial value of false; done means the orchestrator exposes this named capability without enabling WebSocket streaming.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100