ID: 43510 Updated by: paj...@php.net Reported By: dz at bitxtender dot com -Status: No Feedback +Status: Open Bug Type: Streams related Operating System: * PHP Version: 5.2.5
Previous Comments: ------------------------------------------------------------------------ [2009-07-21 13:48:53] david dot zuelke at bitextender dot com Problem still exists in 5.3.0. Will try and come up with a proper .phpt and possibly a patch. Can you reopen in the meantime? ------------------------------------------------------------------------ [2008-11-04 01:00:01] php-bugs at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2008-10-26 23:41:58] dz at bitxtender dot com Thanks Jani. Will try ASAP. ------------------------------------------------------------------------ [2008-10-26 23:34:03] j...@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows: http://windows.php.net/snapshots/ ------------------------------------------------------------------------ [2007-12-06 17:37:54] dz at bitxtender dot com The simple reason why this must work is because one might want to serialize an object with a file pointer, and that can only be done by grabbing the meta data on sleep, and restoring the stream on wakeup. But fopen() on an HTTP resource with r+ of course gives a warning that the stream does not support writing! I stumbled across this when someone pointed out that in Agavi, it's not possible to cache a response that is streaming content from an HTTP resource. Check http://trac.agavi.org/browser/branches/0.11/src/response/AgaviResponse.c lass.php?rev=2205#L55 for some "real-life" code that relies on this ;) Also, it never hurts to have things working 100% properly ;) ------------------------------------------------------------------------ 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/43510 -- Edit this bug report at http://bugs.php.net/?id=43510&edit=1
