> > A little surprised and disappointed. Does really no one have any input
>on
> > this subject?
>
>I don't. I don't find this a curl issue, but more of a PHP issue and I am
>clueless.
>
> > How many subscribers are on this list?
>
>166 addresses right now.

<chuckle>

I've not had to deal with this problem, but I'll suggest this:
If the transfer takes longer than the browser's timeout, then what do you
expect?

Check out ftp://ftp.isi.edu/in-notes/rfc2616.txt - is your client sending an
'Expect' header that you're not responding to?

Alternatively, if you're confident of eventually getting the data, start by
sending back some response headers to your client before invoking cURL to
process the remote response - that should at least tell the client to wait
for the rest of the response. Without that, your client is rightly assuming
it's being ignored.

For a *very* long transfer you might have to send something to the client
every so often to keep it waiting.

Regards,

Paul

P.S. Daniel - you're too modest. I *know* you know some php now - you even
demonstrated that knowledge right here ;)

_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger
http://messenger.msn.co.uk

-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
Received on 2003-03-12