-
Notifications
You must be signed in to change notification settings - Fork 11
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
Consider to use TCP socket for inter process communication #28
Comments
How about using named pipes instead? It might be easier. |
Sounds interesting. However, AFAIK, there is no cross-platform named pipe API. So, I think, we need to limit the supported platform or provide fallback ways if named pipes are adopted as the IPC protocol. |
In Unix the following Python code using anonymous pipes works.
I don't have a Windows environment to test it, but according to the documentation this should also work in Windows. |
Thank you for sharing the code. |
https://docs.rs/os_pipe/latest/os_pipe/ seems to be a cross-platform library for handling pipe creation. Also, it seems that in Rust all file descriptors are inherited by the child process. |
👍 > os_pipe |
Currently, the standard input and output are used to communicate with external program problems and solvers but it turned out that it's not a good design. Because many Python libraries use the standard output as logging and debugging purposes, those are easily conflicting with the kurobako IPC.
By using TCP instead, this issue could be resolved (but it would make the implementation more complicated).
The text was updated successfully, but these errors were encountered: