projects / u / mdw / putty / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3effbcf) | patch
No, I take that back: we _do_ have a mechanism for suppressing reads
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Wed, 14 Sep 2011 09:49:00 +0000 (09:49 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Wed, 14 Sep 2011 09:49:00 +0000 (09:49 +0000)
commita699eb41b9aa738514f36a8e5f3007495a52b05b
tree6bd5b5df21d76739d4bd13ebde05af11dfeb8269tree | snapshot (tar.gz zip)
parent3effbcf21a3e3af6994d9ab112db9ce7ba44bbcecommit | diff
No, I take that back: we _do_ have a mechanism for suppressing reads
from forwarding data sources which will be good enough to last until
we close the socket, in the form of the override_throttle() functions.
So this finishes up the work in r9283, by manufacturing outgoing EOF
in response to incoming CLOSE on all channel types.

git-svn-id: svn://svn.tartarus.org/sgt/putty@9284 cda61777-01e9-0310-a592-d414129be87e
ssh.c diff | blob | blame | history
Local modifications for Simon Tatham's `PuTTY' SSH client and terminal emulator