PuTTY semi-bug disconnect

summary: Better handling of the connection closingclass: semi-bug: This might or might not be a bug, depending on your precise definition of what a bug is.difficulty: tricky: Needs many tuits.blocks: reconnect-autopriority: medium: This should be fixed one day.fixed-in: 2005-01-12 f3b5bddd320ab4ba160bc3a0cae8f4b9e1f6705f (0.58)

Better handling of the connection closing, and of SSH_MSG_DISCONNECT
being received. Ideally we should maintain our own idea of when and
whether we expect to see a closure, and only signal clean
exit when a closure or disconnect arrives that we were expecting. If
one arrives unexpectedly it should count as an ungraceful closure,
display a dialog box containing the text out of MSG_DISCONNECT, and
not close the window unless the user selected "Always".

SGT, 2005-01-11: In fact, SSH is really simple in this
respect: as far as I can tell it's always the client's job
to close the connection, so any closure on the part of the server
counts as unexpected. Unless, that is, it comes after a DISCONNECT.