Redirect output to websocket server
up vote
0
down vote
favorite
Is it possible to redirect the output of an executable to a websocket server using powershell? I tried using the Tee-Object but could only output to file or a variable.
So far I have the websocket and executable working separate, how do I pass the output to the websocket client?
$WS = New-Object System.Net.WebSockets.ClientWebSocket
$CT = New-Object System.Threading.CancellationToken
$Conn = $WS.ConnectAsync("localhost:8080", $CT)
While (!$Conn.IsCompleted) { Start-Sleep -Milliseconds 100 }
#How do I continue here?
$WS.SendAsync(...)
myprocess.exe | Tee -Variable ...
powershell websocket pipe
add a comment |
up vote
0
down vote
favorite
Is it possible to redirect the output of an executable to a websocket server using powershell? I tried using the Tee-Object but could only output to file or a variable.
So far I have the websocket and executable working separate, how do I pass the output to the websocket client?
$WS = New-Object System.Net.WebSockets.ClientWebSocket
$CT = New-Object System.Threading.CancellationToken
$Conn = $WS.ConnectAsync("localhost:8080", $CT)
While (!$Conn.IsCompleted) { Start-Sleep -Milliseconds 100 }
#How do I continue here?
$WS.SendAsync(...)
myprocess.exe | Tee -Variable ...
powershell websocket pipe
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Is it possible to redirect the output of an executable to a websocket server using powershell? I tried using the Tee-Object but could only output to file or a variable.
So far I have the websocket and executable working separate, how do I pass the output to the websocket client?
$WS = New-Object System.Net.WebSockets.ClientWebSocket
$CT = New-Object System.Threading.CancellationToken
$Conn = $WS.ConnectAsync("localhost:8080", $CT)
While (!$Conn.IsCompleted) { Start-Sleep -Milliseconds 100 }
#How do I continue here?
$WS.SendAsync(...)
myprocess.exe | Tee -Variable ...
powershell websocket pipe
Is it possible to redirect the output of an executable to a websocket server using powershell? I tried using the Tee-Object but could only output to file or a variable.
So far I have the websocket and executable working separate, how do I pass the output to the websocket client?
$WS = New-Object System.Net.WebSockets.ClientWebSocket
$CT = New-Object System.Threading.CancellationToken
$Conn = $WS.ConnectAsync("localhost:8080", $CT)
While (!$Conn.IsCompleted) { Start-Sleep -Milliseconds 100 }
#How do I continue here?
$WS.SendAsync(...)
myprocess.exe | Tee -Variable ...
powershell websocket pipe
powershell websocket pipe
edited 2 days ago
asked 2 days ago
Chrille
1,109821
1,109821
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago
add a comment |
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I presume myprocess.exe is generating messages you want to send over WS. To catch and send those messages you can use foreach:
myprocess.exe | foreach { $WS.SendAsync($_) }
You may also create your own cmdlet that will accept input from pipeline
function Send-WS { begin { ...define $WS} process { $WS.Send } End { ..do smth at the end} }
myprocess.exe | Send-WS
Perfect, Thanks!
– Chrille
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I presume myprocess.exe is generating messages you want to send over WS. To catch and send those messages you can use foreach:
myprocess.exe | foreach { $WS.SendAsync($_) }
You may also create your own cmdlet that will accept input from pipeline
function Send-WS { begin { ...define $WS} process { $WS.Send } End { ..do smth at the end} }
myprocess.exe | Send-WS
Perfect, Thanks!
– Chrille
2 days ago
add a comment |
up vote
1
down vote
accepted
I presume myprocess.exe is generating messages you want to send over WS. To catch and send those messages you can use foreach:
myprocess.exe | foreach { $WS.SendAsync($_) }
You may also create your own cmdlet that will accept input from pipeline
function Send-WS { begin { ...define $WS} process { $WS.Send } End { ..do smth at the end} }
myprocess.exe | Send-WS
Perfect, Thanks!
– Chrille
2 days ago
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I presume myprocess.exe is generating messages you want to send over WS. To catch and send those messages you can use foreach:
myprocess.exe | foreach { $WS.SendAsync($_) }
You may also create your own cmdlet that will accept input from pipeline
function Send-WS { begin { ...define $WS} process { $WS.Send } End { ..do smth at the end} }
myprocess.exe | Send-WS
I presume myprocess.exe is generating messages you want to send over WS. To catch and send those messages you can use foreach:
myprocess.exe | foreach { $WS.SendAsync($_) }
You may also create your own cmdlet that will accept input from pipeline
function Send-WS { begin { ...define $WS} process { $WS.Send } End { ..do smth at the end} }
myprocess.exe | Send-WS
answered 2 days ago
Mike Twc
49628
49628
Perfect, Thanks!
– Chrille
2 days ago
add a comment |
Perfect, Thanks!
– Chrille
2 days ago
Perfect, Thanks!
– Chrille
2 days ago
Perfect, Thanks!
– Chrille
2 days ago
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53343628%2fredirect-output-to-websocket-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you share the code you tried? Is the problem to catch std output from the executable?
– Mike Twc
2 days ago
@MikeTwc, I updated the question with my code snippet
– Chrille
2 days ago