Bug #15430 Updated: socket_set_blocking doesn't work

From: Date: Sat, 08 Jun 2002 10:44:38 +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-9833@lists.php.net to get a copy of this message
ID: 15430 Updated by: bool@boolsite.net Reported By: armageddon@raydan.de Status: Open Bug Type: Sockets related Operating System: Windows 2000 PHP Version: 4.1.1 New Comment: It's work for me, but it leaks memory... :o( The problem is analysed actually... :o) Previous Comments: ------------------------------------------------------------------------ [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). ------------------------------------------------------------------------ [2002-02-07 09:43:51] armageddon@raydan.de I'm using Apache1.3.22/PHP4.1.1 on Windows 2000. When I use socket_set_blocking($fp, FALSE); PHP doesn't read any more data from the socket: ... do { if ($ch=fgetc($fp)) echo dechex(ord($ch))." "; ... if ($ch==chr(0x2A)) { ... } sleep(1); ... } while (1); ... This does work with socket blocking enabled but with socket blocking disabled I don't get any more data in my PHP-Script ! ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=15430&edit=1

« previous php.bugs (#9833) next »