-
Notifications
You must be signed in to change notification settings - Fork 900
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 EventLoopSchedulerFactory
#5289
Comments
Hello! I am a junior java developer and this project seems very interesting. This seems like something I could help with. Is this issue still open and would it be alright if I contributed? |
Hi, @LaylaSilbernberg. I'm happy if you can contribute to the feature. |
Excellent @ikhoon! I'll start on it today. |
@LaylaSilbernberg Could you clean up the changes that contain many outputs which we should not check in? |
Yes, I just noticed that. Willdo. |
Is this issue over? |
I have provided a pull request with a solution and I am currently waiting on feedback for this final cleanup. |
Oh I see, thanks for the answer. |
@LaylaSilbernberg My apologies for the oversight on your PR. I'll make sure to review it first thing tomorrow. |
Motivation: A load balancing strategy such as round robin can be used not only in `EndpointSelector` but also elsewhere. For example, in the event loop scheduler, requests can be distributed using round robin to determine which event loop to use. This PR is preliminary work to resolve line#5289 and line#5537
Motivation: A load balancing strategy such as round robin can be used not only in `EndpointSelector` but also elsewhere. For example, in the event loop scheduler, requests can be distributed using round robin to determine which event loop to use. This PR is preliminary work to resolve line#5289 and line#5537
Motivation: A load balancing strategy such as round robin can be used not only in `EndpointSelector` but also elsewhere. For example, in the event loop scheduler, requests can be distributed using round robin to determine which event loop to use. This PR is preliminary work to resolve line#5289 and line#5537
The current event loop scheduler factory only takes
EventLoopGroup
as a parameter which may not be enough to create a sophisticatedEventLoopScheduler
.Let's provide a generalized factory interface so that implementations can create schedulers with more information.
The text was updated successfully, but these errors were encountered: