| Package home | Report new bug | New search | Development Roadmap | Status: Open | Feedback | All | Closed Since Version 1.2.2 |
| Bug #18437 | Possible timeout bug | ||
|---|---|---|---|
| Submitted: | 2011-04-13 12:27 UTC | ||
| From: | alec | Assigned: | alec |
| Status: | Closed | Package: | Net_Socket (version 1.0.10) |
| PHP Version: | Irrelevant | OS: | |
| Roadmaps: | (Not assigned) | ||
[2011-04-13 12:27 UTC] alec
(Aleksander Machniak)
Description:
------------
setTimeout() sets the socket timeout, but doesn't set $this->timeout. Then in readLine() wrong timeout can be used, when you'll change timeout after connection.
Comments
[2011-04-15 02:08 UTC] blueyed
(Daniel Hahler)
The doc for $timeout says that it will wait that long for any data, not that this would be considered an error.
Therefore, setTimeout() refers to another timeout altogether (as far as I understand).
[2011-04-15 19:15 UTC] alec
(Aleksander Machniak)
See timeout.patch in http://pear.php.net/bugs/bug.php?id=18281. The timeout in connect() sets only the timeout for connection, so it shouldn't be used in other places. readLine() should use socket timeout.
[2013-05-15 15:47 UTC] alec
(Aleksander Machniak)
-Status: Open
+Status: Closed
-Assigned To:
+Assigned To: alec
This bug has been fixed in SVN.
If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET).
If this was a problem with the pear.php.net website, the change should be live shortly.
Otherwise, the fix will appear in the package's next release.
Thank you for the report and for helping us make PEAR better.