On 12/13/06, Daniel Stenberg <[EMAIL PROTECTED]> wrote:
>
> My goal with this whole non-blocking work is to allow an application to do
> poll() (or equivalent) on the socket and then have it call libssh2 that would
> deal with what it can deal with and return back without hanging waiting for
> further data, to allow the application to go back to wait in the poll().
> Nothing within libssh2 should ever hang waiting for network traffic in either
> direction if the socket is set non-blocking.

Yes, a blocking read was the only thing that worked for me, which was
a problem, as my app  is multi-threaded and I can not sit in there and
wait for it.

I tried writing a wrapper over libbsh2, but I needed
libssh2_poll_channel_read() so I could know if there was data waiting
to be read. I needed this before I went in with the blocking read, but
this function does not seem to work for me (Filed bug 1588093).

I never tried libssh2_poll(). Did you?

Chris

-- 
E-Mail: Chris Nystrom <[EMAIL PROTECTED]>
Saving the world from web proramming.
http://www.newio.org/ - AIM: nystromchris

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
libssh2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libssh2-devel

Reply via email to