Open
Conversation
Member
|
It makes sense, should the same be done for the server (--listen)? |
Merged
Collaborator
|
I just tested this out and can't seem to make it work. |
Collaborator
|
To be clear, the keep-open works, but not the piping stdin |
Member
|
I guess this doesn't work because |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi -
I have a use case for wscat, where I need to send a message to a remote server, and then leave the connection open, so I can receive the responses. As such, I added a simple "keep-open" flag, which doesn't close the web socket or exit the process after the console is closed. This allows wscat to be used in conjunction with echo/cat/etc and an input pipe:
echo '{"type":"message-type"}' | wscat --keep-open -connect localhost:80Creating a pull request in case this might be useful to others.
Cheers,
-Courtland