Separate reflector endpoints for uploads and downloads
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
In the future, reflector will reside on at least 2 different servers. One will be within AWS (for uploads) and others will be distributed around the world for downloads.
I expect to only have 1 upload and 1 download servers once the work on reflector.go is completed, but the SDK should be able to support this.
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 by reading reflector.go and the SDK code that configures reflector endpoints. Trace how uploads and downloads currently select a reflector, then determine the configuration and request paths needed for separate upload and download servers. Done means the SDK supports the AWS upload reflector and geographically distributed download reflectors described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100