ppalaga commented on issue #496: URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-1008716534
The existing network protocol between mvnd client and the daemon would work without any change even if daemon runs on a different host. What is missing is a discovery mechanism for the clients to find daemon(s) running on other hosts. Currently there is only a local file-based deamon registry implementation: the client looks into that file for existing daemons and the daemons write their busy/idle state and port there. So we need some new mechanism. Perhaps a command line option and/or an env. var for passing the daemon host:port to the client would be enough initially? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
