<response to non-technical bullshit>
You cut and snip my words out of context to make your argument? And patronize under the false pretence of giving "advice".. Really? And you talk about being polite and considerate? You are in no position to lecture anyone on forum etiquette.. ever. And you are certainly not in a position to be patronizing.. One word comes to mind: pathetic.
And your two cents are worth zero to me, or anyone reading this forum to get answers or understand ssh.net for that matter.
And dont worry... I would find better technical advice in google translating a drunk russian hobo ramblings than you guys (or the one person hiding behind two pseudonyms). So thanks, but no thanks..
Mixing up technical terms is just the tip of the iceberg in what is your total lack of insight.. And that explains why you get so defensive right off the bat, protecting your ego because of your insecurities.
I don't make fun of non-native speakers, I am one myself.. But I do make fun of people trying to be smarter than they are.
We are on the same team.. just in different leagues;) But you just dont get it..
And yes.. my late response really is a measure of how little I regard you and your "input".
</response to non-technical bullshit>
To anyone interested in the OP question. You cannot/should not read the response stream before the command has completed. However it wouldn't be too difficult to implement the option to read the response concurrently in a thread safe manner if you need it. I did not as it was a nice to have feature, and not need to have.
You cut and snip my words out of context to make your argument? And patronize under the false pretence of giving "advice".. Really? And you talk about being polite and considerate? You are in no position to lecture anyone on forum etiquette.. ever. And you are certainly not in a position to be patronizing.. One word comes to mind: pathetic.
And your two cents are worth zero to me, or anyone reading this forum to get answers or understand ssh.net for that matter.
And dont worry... I would find better technical advice in google translating a drunk russian hobo ramblings than you guys (or the one person hiding behind two pseudonyms). So thanks, but no thanks..
Mixing up technical terms is just the tip of the iceberg in what is your total lack of insight.. And that explains why you get so defensive right off the bat, protecting your ego because of your insecurities.
I don't make fun of non-native speakers, I am one myself.. But I do make fun of people trying to be smarter than they are.
We are on the same team.. just in different leagues;) But you just dont get it..
And yes.. my late response really is a measure of how little I regard you and your "input".
</response to non-technical bullshit>
To anyone interested in the OP question. You cannot/should not read the response stream before the command has completed. However it wouldn't be too difficult to implement the option to read the response concurrently in a thread safe manner if you need it. I did not as it was a nice to have feature, and not need to have.