Everything

php

curl-multi-info-read not functioning

php.internals

Unnamed Person

22 years ago

Hello!

I am writing a php-cgi server, using curl-multi.  It needs to start a bunch of curl
'threads', and steadily process the results of finished 'threads' and start new ones in
their place.

It seems to be working other than curl_multi_info_read() - this function does not
return any data so I cannot see which curl threads have finished and are ready for
processing.

Looking at the curl.haxx.se curl-lib docs, it doesn't look too complicated (I'm not a C
programmer though!) to implement, seeing as everything else is working.  Perhaps I
have missed something entirely.

I assume it is the same problem as mentioned here:?

http://marc.theaimsgroup.com/?l=php-dev&m=104791992407964&w=2

Thank you in advance for any help or suggestions you can offer, or perhaps even an
ETA on when this function might be finished so I can either wait, or skin the cat
another way.

Warm regards,

Jason

Sterling Hughes

22 years ago

curl_multi_info_read() is currently not working.  I am planning on
getting it working before php5, andi allowing (*), although I don't
have any specific timeframe.

You can use $still_running returned from curl_multi_exec (or perform, i
can't remember what i called the php version) to spawn new connections
if you like...

-Sterling

(*) It shouldn't hold up the release, but I think it should be allowed
as a bug fix, since its currently there, just not implemented, and its
important to the multi interface.

On Mar 17, 2004, at 12:11 AM, jason@neodisco.com wrote:

Andi Gutmans

22 years ago

At 10:48 AM 3/17/2004 -0500, Sterling Hughes wrote:

>curl_multi_info_read() is currently not working.  I am planning on getting
>it working before php5, andi allowing (*), although I don't have any
>specific timeframe.
>
>You can use $still_running returned from curl_multi_exec (or perform, i
>can't remember what i called the php version) to spawn new connections if
>you like...
>
>-Sterling
>
>(*) It shouldn't hold up the release, but I think it should be allowed as
>a bug fix, since its currently there, just not implemented, and its
>important to the multi interface.

Hey,

I plan on release RC1 tomorrow (god willing).
However, it's fine with me to fix this before the final release.

Andi