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

Connection asynchronous operations should use the current context instead of the connection context #5293

Open
vietj opened this issue Sep 2, 2024 · 0 comments
Assignees
Milestone

Comments

@vietj
Copy link
Member

vietj commented Sep 2, 2024

Vertx connection asynchronous API (e.g. HttpConnection#updateSettings(...) use the connection context to create a future to be returned. There are no good reasons for this since the API caller expects callbacks on its own context (the connection context should be used for dispatching events mostly).

@vietj vietj self-assigned this Sep 2, 2024
@vietj vietj added this to the 5.0.0 milestone Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant