Support passing murex data types down the pipeline for communication with execs outside of murex about murex HOT 4 CLOSED

I'm now thinking of scraping the original plan and work on a completely different model where data types are channelled via TCP/IP APIs (possibly just using HTTP because it's easier?). This means data types can be stored and forwarded to all CLI tools - even those that aren't aware of murex.

The down side is it turns murex into a server.

More consideration will be needed but in the meantime the existing code will need to be removed.

from murex.

Nearly a year has passed and I'm still at a loss about how to pass data-type information down the pipeline. I'm starting to wonder if this is one of those behaviours that is best left ignored rather than having a pseudo-solution that works in some situations but not all and creates other unexpected results.

from murex.

After rethinking about this recently, it occurred to me that the answer is really very simple: create another two file descriptors. 4 for data-type in, and 5 for data-type out.

I should also create a new pipe to disable the creation of those descriptors. Or maybe add a differentiator where | is a traditional pipe and -> creates those fd's? Or maybe => disables them?

This will need some thought and testing to see the performance impact of adding two new descriptors per each exec.

I will also need to add some builtins to murex to export descriptors. Or better yet, if an environmental variable is set (eg MUREX_DATA_TYPE) then automatically assume there to be additional fd's? In fact, if we are to write an environmental variable anyway, then perhaps create one for the input data type and only use one fd for the exported data type?

from murex.

This will be included in version 3.0.x release

from murex.