On Sun, 19 Dec 2010, Felix E. Klee wrote:
I plan to write a daemon that will download data from web services
(HTTP) and write it to a database. And I wonder if I would run into a
problem if the database operations in CURLOPT_WRITEFUNCTION take very
long. Some questions:
* When CURLOPT_WRITEFUNCTION is executed, all parallel downloads are
paused - right?
If you're using the multi interface, then yes each call to the
CURLOPT_WRITEFUNCTION will block all transfers.
* If CURLOPT_WRITEFUNCTION takes, say, 10 seconds, would that be a
problem? When does the average remote server become impatient and
close a connection?
I think HTTP servers tend to wait one or more minutes, FTP servers tend to
wait many minutes, NATs and firewalls tend to allow many minutes etc. I don't
think 10 seconds is going to cause a problem for most cases.
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
