On Wed, 19 Dec 2001, Hrvoje Niksic wrote:
> > You could solve it with a plain and simple alarm() and a signal
> > handler. It would work on pretty much all unix-systems...
>
> That's true. Again, I just never saw the point. I assume you didn't do
> that in libcurl because you didn't want to muck around with signals from
> within the library?
We used that aproach until we replaced it with non-blocking connects
completely. People wanted timeouts and that was the only method I knew could
offer that before we made the connects non-blocking.
We still use signals to abort name lookups pre-maturely, although we try to
ducment that it isn't gonna work in multi-threaded systems, or systems
without signals (like windows).
--
Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
