lubURL nuances

[Josh Mellicker]

FWIW, we have mostly migrating from libURL to using cURL for downloads and uploads. The nice thing about cURL is that if there is a disconnect 90% of the way through transferring a large file, cURL will resume from where it left off. Also it seems rock solid and reliable.


On Mar 11, 2010, at 5:23 AM, Richard Gaskin wrote:

> While working with Dan Friedman to diagnose some FTP issues, he came up with some questions I couldn't answer so I'm bringing them to y'all to see what we can find:
> 
> 1. Is "put url..." a blocking command?
>   I believe it's supposed to be, but find I can sometime do other
>   things while it's running, including submitting subsequent
>   "put url..." commands.
> 
> 2. In such a circumstance, the second attempt to "put url..."
>   meets with an error, "Previous request not completed."  I've
>   found that once that error hits the original request sometimes
>   runs into trouble, requiring me to use libUrlResetAll and
>   try again.  Is there a more graceful way to handle that error?
> 
> 3. libUrlResetAll comes with a warning not to use it. :)  But I've
>   found it the simplest, most reliable way to cancel all socket
>   activity and start fresh.  If that's your goal, to reset all
>   socket stuff and start fresh, is there some downside to using
>   libUrlResetAll that I've overlooked?
> 
> TIA -
> 
> --
> Richard Gaskin
> Fourth World
> Rev training and consulting: http://www.fourthworld.com
> Webzine for Rev developers: http://www.revjournal.com
> revJournal blog: http://revjournal.com/blog.irv
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution