Coprocess Protocol V2

Design Constraints

• Command line tools written in any langauge should be convertible to coprocesses.
• The patches required to do this must be small and localized.
  • For example, we shouldn't require modifying every print statement in the program and its dependencies!
  • There shouldn't be any special cases, e.g. for handling stdin, stderr, EOF, etc.

The initial Coprocess Protocol Proposal would require too much modification to existing tools. It was more like my 2012 projects fly and xmap. That only handled command line tools that behaved in a particular way.

Observations

• We do not control every print statement in the program.

  • Python interpreter prints stack traces to stderr.
  • Most VMs, e.g. Python or the JVM, print their own messages to stderr in rare cases, e.g. in out of memory conditions.
  • if you build with ASAN, this should work too.
  • It would be annoying to change every single print() statement in a Python program to print(msg, file=fcli_out).

• Just knowing sending stdin/stdout/stderr

Both of these should work, and they are different:

foo.py < in.txt >out.txt 2>err.txt

foo.py < in.txt >out-err.txt 2>&1

In the first case, the process is started with three files connected to its 3 descriptors.

In the second case, the process is started with two files connected to its 3 descriptors.

TODO

• Signals? If you Ctrl-C in the client process, can it kill the whole coprocess?