This option sets the default value for the timeout, as though you manually called stream_set_timeout on the stream.
The behavior is equivalent to using select() to wait for up to the timeout duration prior to a read or write operation. PHP does not implement "idle" timeouts; that's an application level behavior. It should be noted that a timeout in this sense can be a transient condition in the case of a read operation, it does not necessarily indicate that the connection is bad, just that no new data is available within the time allotted. More general streams bits here that may or may not be apparent from the docs: http://www.slideshare.net/wezfurlong/php-streams-lucky-dip --Wez. On Tue, Jul 7, 2009 at 5:48 AM, Hannes Magnusson<hannes.magnus...@gmail.com> wrote: > On Thu, Jul 2, 2009 at 01:01, Brian A. > Seklecki<sekle...@noc.cfi.pgh.pa.us> wrote: >> All: >> >> Perhaps we should clarify the socket tuneables such as: >> >> ; Default timeout for socket based streams (seconds) >> default_socket_timeout = 60 >> >> These are slightly ambiguous. e.g., we should clarify connect() >> timeouts v.s. "idle" timeouts. > > Anyone that knows the answer to this? > > >> There are at least a dozen tickets open related to timeout behavior and >> a lot of the confusion results of ambiguity in the variable naming >> convention and documentation. > > Could you post the ones you know of here please? > > -Hannes > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
