When we are asked to unthrottle an SSH connection (by the front end
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 12 May 2012 17:00:54 +0000 (17:00 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sat, 12 May 2012 17:00:54 +0000 (17:00 +0000)
commit78e71de13e688b0aef0128115c0f23d5d52b5aa7
tree5ae561d93ac0cbd1220b62137535a2eb7df0cdde
parent142228d2e0cc0729b6527a00c56a6e38edb290c1
When we are asked to unthrottle an SSH connection (by the front end
calling back->unthrottle), we should immediately call
ssh_process_queued_incoming_data to handle the SSH packets that have
been saved for later functioning while we were throttled. Otherwise,
they'll sit there unhandled until the next call to ssh_gotdata, which
might not be for ages if the server thinks it's waiting for us.

git-svn-id: svn://svn.tartarus.org/sgt/putty@9523 cda61777-01e9-0310-a592-d414129be87e
ssh.c