-
Notifications
You must be signed in to change notification settings - Fork 32
Implement --close #73
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
base: main
Are you sure you want to change the base?
Conversation
bikeshed: the |
Hm, --close is confusing I think. --one-way is better, but it also is not clear which way, given that the listener could send or receive data. How about something like --recv-only or --send-only? |
maybe |
Is
|
I think --recv-only is nicest. It leaves the door open for --send-only if we ever need it, and can be used on both sides if ever needed. |
This option causes the sending side to not send any data and instead immeditally send an EOF. This can be useful when you are only interested in sending data in one direction. Closes n0-computer#10
src/main.rs
Outdated
@@ -323,7 +331,11 @@ async fn listen_stdio(args: ListenArgs) -> Result<()> { | |||
snafu::ensure_whatever!(buf == dumbpipe::HANDSHAKE, "invalid handshake"); | |||
} | |||
tracing::info!("forwarding stdin/stdout to {}", remote_node_id); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe update this log line accordingly as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good suggestion, thanks. the latest commit updates this message
This option causes the sending side to not send any data and instead immeditally send an EOF. This can be useful when you are only interested in sending data in one direction.
Closes #10