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

[Nit] Add note to why DWNs should be tried in-order #176

Open
esgoode opened this issue Jun 29, 2022 · 1 comment · May be fixed by #177
Open

[Nit] Add note to why DWNs should be tried in-order #176

esgoode opened this issue Jun 29, 2022 · 1 comment · May be fixed by #177
Labels
artifact: spec intended for the actual specification stage: in progress this ticket is in progress

Comments

@esgoode
Copy link

esgoode commented Jun 29, 2022

Parse the DecentralizedWebNode Service Endpoint object and select the first URI present in the serviceEndpoint objects nodes array. NOTE: implementers SHOULD select from the URIs in the nodes array in index order.*

*DWNs SHOULD be tried in order because DWNs SHOULD be ordered by availability
@esgoode
Copy link
Author

esgoode commented Jun 30, 2022

#177

@andorsk andorsk linked a pull request Mar 11, 2023 that will close this issue
Clarify node resolution ordering #177
Open
@andorsk andorsk added stage: in progress this ticket is in progress artifact: spec intended for the actual specification labels Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
artifact: spec intended for the actual specification stage: in progress this ticket is in progress
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify node resolution ordering esgoode/decentralized-web-node
2 participants
@andorsk @esgoode