Date: 04/29/98
- Next message: rasmus: "[PHP-DEV] CVS update: php3"
- Previous message: info <email protected>: "[PHP-DEV] Bug #329: inconsistency with if-elseif-else-endif loops"
- In reply to: rasmus: "[PHP-DEV] CVS update: php3/functions"
- Next in thread: zeev: "[PHP-DEV] CVS update: php3/functions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[rasmus <php-dev <email protected>>]
|
| Ok, the set_block() function has been fully implemented and tested.
| Seems to work nicely. My test script follows. Changing the
| set_block() argument changes the output from this dramatically
| script.
|
| $fp = fsockopen("207.164.55.5",80);
| set_block($fp,0);
| fputs($fp,"HEAD / HJTTP/1.0\n\n");
| while(!feof($fp)) {
| echo fgets($fp,200);
| echo "loop\n";
| }
What about calling it set_blocking() instead? set_block() sounds to
me like something related to block sizes.
- Stig
-- Stig S. Bakken Guardian Networks AS mailto:ssb <email protected> Trondheim, Norway http://www.pvv.org/~ssb/ http://www.guardian.no/
- Next message: rasmus: "[PHP-DEV] CVS update: php3"
- Previous message: info <email protected>: "[PHP-DEV] Bug #329: inconsistency with if-elseif-else-endif loops"
- In reply to: rasmus: "[PHP-DEV] CVS update: php3/functions"
- Next in thread: zeev: "[PHP-DEV] CVS update: php3/functions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

