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

Add blocking mode #50

Open
nicholaschiasson opened this issue Sep 21, 2020 · 0 comments
Open

Add blocking mode #50

nicholaschiasson opened this issue Sep 21, 2020 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@nicholaschiasson
Copy link
Owner

Depends on #48

Blocking mode? For real? Are you serious? I know, it sounds crazy, but I think it should be an option.

Add a directive attribute blocking which when passed will cause the peer init handler to use ngx_parse_url instead of the configured resolver.

The reasons I think this is important are a bit complicated and come down to DNS resolution stability differences between using differing resolvers during runtime... Using this blocking option would ensure the DNS resolution each interval uses the same resolver (I suppose the system one?) as the one used during initialization.

@nicholaschiasson nicholaschiasson added enhancement New feature or request help wanted Extra attention is needed labels Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant