ID: 47629
User updated by: danielc at analysisandsolutions dot com
Reported By: danielc at analysisandsolutions dot com
Status: Open
Bug Type: MySQLi related
Operating System: Windows XP SP3
PHP Version: 5.3CVS-2009-03-12 (snap)
Assigned To: pajoye
New Comment:
I'll put together tests of the various functions and report back.
Previous Comments:
------------------------------------------------------------------------
[2009-06-21 09:04:11] paj...@php.net
"1) That's how PHP 5.2 does it."
Not really relevant in this case.
"2) That's how the other socket functions do it in 5.2 and 5.3."
Then there is a bug here.
"3) The timeout is from communication with another entity, not from
the
script itself."
The max_execution_time has the highest priority and should always has
it. If it is not the case in one function or another then there is a bug
in this function.
------------------------------------------------------------------------
[2009-06-21 00:48:41] danielc at analysisandsolutions dot com
Because:
1) That's how PHP 5.2 does it.
2) That's how the other socket functions do it in 5.2 and 5.3.
3) The timeout is from communication with another entity, not from the
script itself.
------------------------------------------------------------------------
[2009-06-20 20:12:24] paj...@php.net
but there is no bug here. Why do you want to let the socket timeout
override the main timeout?
------------------------------------------------------------------------
[2009-06-20 17:34:32] dani...@php.net
Yes, the execution timeout makes sense some ways. The problem is the
behavior is inconsistent between 5.2 and 5.3 and between other
connection functions.
------------------------------------------------------------------------
[2009-06-20 13:19:04] paj...@php.net
With:
max_execution_time: 2
default_socket_timeout: 6
It is the expected behavior to have a fatal error about the maximum
execution time being exceeded. max_execution_time has the highest
importance.
------------------------------------------------------------------------
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/47629
--
Edit this bug report at http://bugs.php.net/?id=47629&edit=1
