Skip to content
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

StdioConfig File Pipes #89

Open
Aidan63 opened this issue Apr 6, 2024 · 0 comments
Open

StdioConfig File Pipes #89

Aidan63 opened this issue Apr 6, 2024 · 0 comments
Labels

Comments

@Aidan63
Copy link
Owner

Aidan63 commented Apr 6, 2024

The StdioConfig type allows you to ignore or pipe output from a process, but there are also two extra ones to pipe straight to a file path or an already opened file. Why are files the ones allowed here, what if I want to pipe straight out of a socket, or what if I want to pipe straight into my own custom IWritable. It seems odd that file is the only special case here.

We could add extra config options for these other cases but at that point it might be better to provide a more generic pipe mechanism as currently the user can't, say, automatically send a file through a socket. This would also greately reduce the complexity of the process implementation.

Alternatively don't provde any fancy pipe stuff and let the user do it themselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant