-----Original Message-----
From: Daniel Stenberg
Sent: Monday, February 02, 2004 10:25 AM

> There are work-arounds:
> ...
> 3. use a second task that kills the first curl process in case it runs
too
> long

I don't suppose a multi-threaded solution could solve this problem? E.g.
on windows, run the nameresolve within another thread, and if the user
requests -m, have curl watch it's own (asynchronous?) thread and kill it
if it runs too long?

I don't possess the knowledge of how to actually code this, but has this
approach been considered? Would it work, if someone with the right
knowledge could find the time to code it up?

- Kevin

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Received on 2004-02-02