@Festive,
I'm far from perfect with this library. If you find a sure-fire way to make asynch.IsComplete() work, I'm your disciple!
Frankly, my suspicion is that SSH, or any client in a 'shell' environment for I/O, really can't have any way of knowing whether the stream response is done.
A good example included the *nix 'tail' command, and any Windows equivalents (I guess ping with lots of iterations would be close). I say this because even after a particular shell returns the prompt, it may not be done yielding content. I hope that makes sense to someone out there... :)
As for Java, you have to respect her. She's STILL the only truly OO language there is. Unfortunately, all high level languages today have to have 'interpreters', which convert source to intermediate language (MSIL is no exception), so virtually no programmer today programs against the CPU/HW they are using. That has brought about a whole other set of problems, where quality of developers as suffered from making programming more like block diagrams and dummy lights. MS has it's own version of this in VS, called LightSwitch...
Anyway, I hope you can make progress, and post back a better way for us to use this library! :)
pat
:)
I'm far from perfect with this library. If you find a sure-fire way to make asynch.IsComplete() work, I'm your disciple!
Frankly, my suspicion is that SSH, or any client in a 'shell' environment for I/O, really can't have any way of knowing whether the stream response is done.
A good example included the *nix 'tail' command, and any Windows equivalents (I guess ping with lots of iterations would be close). I say this because even after a particular shell returns the prompt, it may not be done yielding content. I hope that makes sense to someone out there... :)
As for Java, you have to respect her. She's STILL the only truly OO language there is. Unfortunately, all high level languages today have to have 'interpreters', which convert source to intermediate language (MSIL is no exception), so virtually no programmer today programs against the CPU/HW they are using. That has brought about a whole other set of problems, where quality of developers as suffered from making programming more like block diagrams and dummy lights. MS has it's own version of this in VS, called LightSwitch...
Anyway, I hope you can make progress, and post back a better way for us to use this library! :)
pat
:)