On Fre 09.09.2005 23:06, Daniel Stenberg wrote:
>On Fri, 9 Sep 2005, Alexander Lazic wrote:
>
>Possibly it should just trust the application and don't do any select/poll
>at all!

Ok.

>>The app must know which are his own sockets an which are the libcurl
>>sockets, imho.
>
>Oh yes it really should, since among other things it should tell
>libcurl when action has been dected on libcurl's sockets and not
>otherwise.

Hm do you mean that libcurl also call the (*curl_socket_callback) for
they sockets?

>First, this curl_multi_socket() thing of course implies using the multi
>interface.

Sure, sorry.

>But then, why would the application care or even want to know about the
>connect/handshake status of each connection? It makes no difference to
>it.

Hm if the callback get CURL_POLL_(IN|OUT|INOUT) then the app can
read()/write() to the socket, right?

I think i can't help you for this, because i'am not sure that i have
understand the hole idea behind the curl_multi_socket() :-(

Greetings

al ;-)
Received on 2005-09-10