|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #37638 Socket flags...
Submitted: 2006-05-30 06:49 UTC Modified: 2021-04-06 14:32 UTC
From: aeolianmeson at blitzeclipse dot com Assigned: cmb (profile)
Status: Feedback Package: Sockets related
PHP Version: 5.1.4 OS: Fedora 5
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: aeolianmeson at blitzeclipse dot com
New email:
PHP Version: OS:


 [2006-05-30 06:49 UTC] aeolianmeson at blitzeclipse dot com
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.



Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2016-12-30 23:44 UTC]
-Package: Feature/Change Request +Package: Sockets related
 [2021-04-06 14:32 UTC]
-Status: Open +Status: Feedback -Assigned To: +Assigned To: cmb
 [2021-04-06 14:32 UTC]
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?
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat Apr 17 18:01:24 2021 UTC