05-23-2024, 05:12 AM
(This post was last modified: 05-23-2024, 05:14 AM by DSMan195276.)
(05-23-2024, 04:44 AM)madscijr Wrote: Thanks for your reply - those examples are nice and short, I look forward to giving them a try."pipe" refers to either a Unix pipe or a Windows Anonymous Pipe. They have different APIs but functionally achieve the same thing, you call a function that gives you back two handles that make up a "pipe", where one is the "read handle" and the other the "write handle". You can read/write to these handles like regular files, and any data written to the "write handle" will show up as data to read from the "read handle".
By "pipe" do you mean one prog calling another with command line args, or something else, like a program sending args to a different application already running?
Thanks again!
Through various methods you can pass the "write handle" to your client program and keep the "read handle" in your host program, this allows the client program to write data to the "write handle" that the host can receive via reading from the "read handle". It effectively achieves exactly what my example did but removes the need to introduce any networking (which simplifies the process and removes some potential failure points).