Hi Dustin, None. ssh_set_blocking() makes the whole session non-blocking so it impacts all other libssh calls you may make on this session, until you call ssh_set_blocking(1) back.
Aris Le 9/09/13 17:07, Dustin Oprea a écrit : > Now, what's the difference in calling ssh_set_blocking(0) before > ssh_channel_read(), and just calling ssh_channel_read_nonblocking()? > > Dustin > > On Sep 9, 2013 10:45 AM, "Andreas Schneider" <[email protected] > <mailto:[email protected]>> wrote: > > On Friday 06 September 2013 20:39:01 Dustin Oprea wrote: > > The ssh_set_blocking() call currently has the following > disclaiming in the > > "master" documentation: > > > > nonblocking code is in development and won't work as expected > > > > > > This surprised me. Since there are dozens of functions that support > > non-blocking mode (by returning SSH_AGAIN when necessary), I thought > > non-blocking mode would've been an established feature. > > Thanks for the hint. Yes, with libssh 0.6.0 this should be fully > functional. > I've removed the comment. > > > -- andreas > > > -- > Andreas Schneider GPG-ID: F33E3FC6 > www.cryptomilk.org <http://www.cryptomilk.org> > [email protected] <mailto:[email protected]> > >
