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

Dynamically find Grpc port #84

Open
Brandhoej opened this issue Oct 30, 2022 · 0 comments
Open

Dynamically find Grpc port #84

Brandhoej opened this issue Oct 30, 2022 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Brandhoej
Copy link
Contributor

GrpcServer per #74 now uses port 9000. However, I believe we should prioritize this port, or another one, but if it is already in use then we should select another one dynamically. For inspiration this and this, the important aspects is the general approach for finding the available port by using port 0. We also need to consider configuration for automatic deployment in an unknown environment. Given that j-Ecdar is designed as a server, we cannot always listen to a random port as the server may be configured in such a way that it relies on j-Ecdar stopping if the port is unavailable. Because of this we must also provide a way to configure j-Ecdar not to choose a random available port.

@Brandhoej Brandhoej added enhancement New feature or request good first issue Good for newcomers labels Oct 30, 2022
@Brandhoej Brandhoej mentioned this issue Oct 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant