Broken Response in Asyncronous Connection (wodSSH / wodSSH.NET)

by wodSupport, Thursday, December 11, 2014, 16:37 (3416 days ago) @ Mike D

Mike,

hi. It's normal buffer is 'fragmented'. As data arrives, we provide it to the application. You cannot know how much data is sent in each packet, since this all depends on the server.

You should queue it by yourself in the buffer, and then use when it's suitable for you. That is, for example, how our WaitFor method works.

So, instead of

Debug.print Ssh1.Receive

you should do

a = a + Ssh1.Receive

and then check variable a which contains full received data for some string that should appear inside (such as command prompt).

In any case, that's normal. SSH protocol (or Telnet protocol) don't know about 'buffering' or 'command execution' or something similar. It known only about data flying over from one side to another. Higher logic (bash, command.exe, sh, etc) takes care of using it as commands and their responses.

Best regards,
Kreso

locked

3670 views

Complete thread:

Broken Response in Asyncronous Connection - Mike D, 2014-12-11, 16:33
- Broken Response in Asyncronous Connection - wodSupport, 2014-12-11, 16:37

Thank you very much for the rapid responses. I was a little nervous about dealing with a company that is on a different continent from me. You have proven my concerns to be unfounded.

Robert Pacheco

Surebridge, Inc.

Your support is fantastic.

Douglas Michael Panchyshyn

The Net Software Group

May I say how nice it is to work with components so complete and self-explanatory that using them in my application is as instinctive as though I wrote them myself?

Michael Barnett

Full Spectrum Telecommunications