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.

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

did:web resolve bring-your-own-client #96

Open
KendallWeihe opened this issue Feb 28, 2024 · 1 comment
Open

did:web resolve bring-your-own-client #96

KendallWeihe opened this issue Feb 28, 2024 · 1 comment

Comments

@KendallWeihe
Copy link
Contributor

Our did:dht implementation enables consumers to bring-their-own-clients

But our did:web resolver just uses the native http.Get() call. Not sure exactly what this would look like, or if this even makes sense (also relevant to this ticket #94), but if we're enabling developer-defined clients in did:dht then we should do the same in did:web.

@KendallWeihe
Copy link
Contributor Author

Relevant for configuring timeout settings, as none are set by default https://blog.cloudflare.com/the-complete-guide-to-golang-net-http-timeouts#client-timeouts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant