> -----Original Message-----
> From: libssh2-devel-bounces_at_cool.haxx.se
> [mailto:libssh2-devel-bounces_at_cool.haxx.se] On Behalf Of
> Daniel Stenberg
> Sent: Tuesday, April 13, 2010 5:39 PM
> To: libssh2 development
> Subject: RE: libssh2 hangs in channel_close()
>
> Right, but that conclusion lumps together the *sending* of
> SSH_MSG_CHANNEL_EOF with the *waiting* for
> SSH_MSG_CHANNEL_EOF, and I'm curious if that really has any merit.
Just take a look at http://www.ietf.org/rfc/rfc4254.txt, and found it said "A party MAY send SSH_MSG_CHANNEL_CLOSE without having sent or received SSH_MSG_CHANNEL_EOF". Maybe Peter added the waiting code to cater to latter part of "sent or received SSH_MSG_CHANNEL_EOF".
Peter, any comment?
Thanks,
Xu Qiang
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2010-04-13