ID: 23838 Updated by: [EMAIL PROTECTED] Reported By: dietrich dot ayala at foundstone dot com -Status: Open +Status: Assigned Bug Type: Sockets related Operating System: windows 2000 PHP Version: 4.3.2RC4 Assigned To: wez New Comment:
Can not reproduce on Linux. (no script to test with) Not really critical, it's just some streams thingie. :) Previous Comments: ------------------------------------------------------------------------ [2003-05-27 14:48:53] [EMAIL PROTECTED] Assigning to myself; it would be good if some other people could verify if this problem exists on other platforms, and if this is a critical issue. ------------------------------------------------------------------------ [2003-05-27 12:57:20] dietrich dot ayala at foundstone dot com 1. it doesn't seem to be doing non-busy waits. If the remote host takes a long time to respond, the CPU is still maxed until a response is received. 2. I've had repeatable situations where the server returned a response right away, but stream_select() didn't return for (in our repeatable case) 10 mins. What's it's criteria for responding? What will it do if I pass a stream to it, which has already had everything read from it, but is persistent, so there's no EOF/line-break/anything? It seems that whatever its return criteria is, it isn't met sometimes. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=23838&edit=1
