Req #37638 [Fbk->NoF]: Socket flags...
Edit report at https://bugs.php.net/bug.php?id=37638&edit=1
ID: 37638
Updated by: php-bugs@lists.php.net
Reported by: aeolianmeson at blitzeclipse dot com
Summary: Socket flags...
-Status: Feedback
+Status: No Feedback
Type: Feature/Change Request
Package: Sockets related
Operating System: Fedora 5
PHP Version: 5.1.4
Assigned To: cmb
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2021-04-06 14:32:12] cmb@php.net
EWOULDBLOCK is not a flag, but rather an error number, and it is
available as SOCKET_EWOULDBLOCK. So I don't understand what you
are requesting. Can you please clarify?
------------------------------------------------------------------------
[2006-05-30 06:49:59] aeolianmeson at blitzeclipse dot com
Description:
------------
Apparently there are flags that various socket calls will use. One in particular is the EWOULDBLOCK
flag-- It indicates if an accept(), close(), etc.. would've blocked, if blocking was currently
disabled.
Not having any C socket experience, I'm not exactly sure how the flags are accessed, but it
would be convenient to have them, since there are so many different variables when dealing with
sockets that are required to make sure the entire process works.
Dustin
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=37638&edit=1
Thread (3 messages)