On Thu, Nov 06, 2003 at 10:56:07PM +0100, Daniel Stenberg wrote:
> On Thu, 6 Nov 2003, Wei Weng wrote:
>
> > Try to unplug the cable in the middle of transfer, you will see that the
> > progress function gets called over and over again, the message gets printed
> > out. And if you plug the cable back in, the transfer resumes, and goes on.
>
> That is what I would assume it should do. The progress callback is called
> about once per second, even if nothing at all is transfered.
>
> > Please DO NOT fix it if you think libcurl should have quitted. :)
>
> I don't see why libcurl should have quit? Pulling the plug does not kill the
> connection, it just makes it pause.
>
> > This particular behavior is quite userful to me, but if we can have some
> > better control, (such as an option of setting how many times libcurl is
> > going to "retry") it is even better!
>
> Again: libcurl doesn't retry at all, so I don't know what you mean here.

It sounds like regular TCP retries done by the kernel.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/