cloudflare / cloudflare/moq-rs
draft-07: Serve Fetch responses from local cache in moq-relay-ietf
- Dominant language
- Rust
- Stars
- 166
- Forks
- 59
- Avg merge
- 18h 21m
- Merged PRs (30d)
- 22
Description
We have basic encoding/decoding for Fetch control messages already, but don't yet properly respond to them when we receive them in `moq-relay-ietf`.
Fully implementing Fetch requires us to have a local cache and to also correctly determine when and how we need to go upstream to fill that cache with additional objects.
We should probably work towards serving Fetch response by first tackling these other issues:
- https://github.com/englishm/moq-rs/issues/61
- https://github.com/englishm/moq-rs/issues/58
- https://github.com/englishm/moq-rs/issues/57
- https://github.com/englishm/moq-rs/issues/59
Contributor guide
Research direction
Start by reviewing the existing Fetch control-message encoding and decoding in moq-relay-ietf, then read issues 61, 58, 57, and 59 for the prerequisite cache and upstream-fetch work. Done means the relay can maintain a local cache, fetch additional objects upstream when needed, and serve Fetch responses from that cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100