Bug #15430 Updated: socket_set_blocking doesn't work

From: Date: Tue, 18 Jun 2002 23:18:33 +0000
Subject: Bug #15430 Updated: socket_set_blocking doesn't work
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-11282@lists.php.net to get a copy of this message
ID: 15430 Updated by: sniper@php.net Reported By: armageddon@raydan.de -Status: Duplicate +Status: Closed Bug Type: Sockets related Operating System: Windows 2000 PHP Version: 4.1.1 New Comment: This bug has been fixed in CVS. You can grab a snapshot of the CVS version at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2002-06-08 07:10:59] armageddon@raydan.de Why "Duplicate" ? The other report is about a memory leak and mine is about PHP doesn't read data from the socket when using non-blocking sockets. ------------------------------------------------------------------------ [2002-06-08 06:55:03] mfischer@php.net Wierd duplicate of http://bugs.php.net/?id=15485&edit=1 ------------------------------------------------------------------------ [2002-06-08 06:44:38] bool@boolsite.net It's work for me, but it leaks memory... :o( The problem is analysed actually... :o) ------------------------------------------------------------------------ [2002-04-06 15:05:52] armageddon@raydan.de Re: ruehl@igd.fhg.de This doesn't work for me :-( I still don't get any date when I use non-blocking sockets... ------------------------------------------------------------------------ [2002-03-14 08:09:15] ruehl@igd.fhg.de I have currently the same problem with PHP 4.1.1. However, when I put the sleep(1) statement IN FRONT of the fgets() or fgetc(), my code works even with non-blocking sockets (it's annoying but it works). Maybe this helps you for now (until this bug has been fixed). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15430 -- Edit this bug report at http://bugs.php.net/?id=15430&edit=1

« previous php.bugs (#11282) next »