On Mon, 2011-04-25 at 15:26 -0500, Daniel Stenberg wrote:
> On Mon, 25 Apr 2011, Paul Albrecht wrote:
>
> > I need the option set when the socket is created so CURLOPT_SOCKOPTFUNCTION
> > (setsockopt) is too late. I'll try the CURL_OPENSOCKETFUNCTION (socket)
> > which should work, but why is the callback necessary? Shouldn't this be the
> > default? Why would I want the connect socket propagated to a forked process?
>
> Can you enlighten us when exactly this would cause anyone problems?
>

Bound addresses and file descriptors are wasted while the process runs
and that's a problem if it runs for long time.

-- 
Paul Albrecht
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html