Parent <-> child communication design. #1025
Replies: 1 comment
-
Named pipes are bidirectional, so you don't need each process to create both a server and a client pipe. The parent process should create a named pipe and all child processes can connect to it as clients. Now each client has a bidirectional stream with the parent, over which JSON-RPC can be done. Once the connection is established, you can and should use it for all your JSON-RPC messages. Don't recreate the stream after each processed message. Here is a sample named pipe server that can accept multiple clients: |
Beta Was this translation helpful? Give feedback.
-
Hi,
My case: launcher application that is able to spawn 2 child apps. I want my launcher and child apps be able to talk to each other via json rpc, meaning sending multiple messages back and forth when needed. Based on od cond sampes I implemented it this way:
is that the way to go for this case?
Beta Was this translation helpful? Give feedback.
All reactions