Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More usable LB policy in 302 backend #3

Open
ZenithalHourlyRate opened this issue Mar 2, 2021 · 0 comments
Open

More usable LB policy in 302 backend #3

ZenithalHourlyRate opened this issue Mar 2, 2021 · 0 comments

Comments

@ZenithalHourlyRate
Copy link
Contributor

Currently an exprimental 302 backend is deployed, you may use https://mirrors.mirrorz.org or its alias https://m.mirrorz.org (unavailable when posting this issue because of DNS) or https://mirrors.zenithal.workers.dev to play with it.

As suggested in README.md of directory /302, the current Newest policy is not optimal for users. Hence this issue is opened for discussion on this topic.

We may do the following things here:

  1. Propose new policy and its needed information/metadata
  2. Discuss what the Monitor should collect
  3. Discuss the metadata that that protocol mirrorz.json should provide
  4. Post your experiences/feeling about using https://mirrors.mirrorz.org
@ZenithalHourlyRate ZenithalHourlyRate transferred this issue from mirrorz-org/mirrorz Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ZenithalHourlyRate