You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7153 Reporter: mwm Status: closed (set by @xavierleroy on 2017-09-24T15:33:02Z) Resolution: fixed Priority: normal Severity: tweak Version: 4.02.3 Target version: 4.04.0 +dev / +beta1 / +beta2 Fixed in version: 4.04.0 +dev / +beta1 / +beta2 Category: otherlibs
Bug description
While the Unix library exports the SOCK_SEQPACKET connction type, it fails to export anything allowing it to be used. In particular, the message flag MSG_EOR (used to mark and detect the end of a packet) isn't there. Worse yet, there's apparently no API for reading from a socket that lets you check the message flags for MSG_EOR (or I couldn't find it, in which case the documentation might be improved).
Given that the SEQPACKET connection type isn't widely implemented, and may only be supported for odd protocol families, possibly the best solution is to simply remove it.
Steps to reproduce
Read the documentation on the Unix library.
The text was updated successfully, but these errors were encountered:
Documented the issue, commit [trunk 4515477]. We could improve support for SOCK_SEQPACKET by binding the recvmsg() and sendmsg() system calls. But it's probably not worth the effort.
Original bug ID: 7153
Reporter: mwm
Status: closed (set by @xavierleroy on 2017-09-24T15:33:02Z)
Resolution: fixed
Priority: normal
Severity: tweak
Version: 4.02.3
Target version: 4.04.0 +dev / +beta1 / +beta2
Fixed in version: 4.04.0 +dev / +beta1 / +beta2
Category: otherlibs
Bug description
While the Unix library exports the SOCK_SEQPACKET connction type, it fails to export anything allowing it to be used. In particular, the message flag MSG_EOR (used to mark and detect the end of a packet) isn't there. Worse yet, there's apparently no API for reading from a socket that lets you check the message flags for MSG_EOR (or I couldn't find it, in which case the documentation might be improved).
Given that the SEQPACKET connection type isn't widely implemented, and may only be supported for odd protocol families, possibly the best solution is to simply remove it.
Steps to reproduce
Read the documentation on the Unix library.
The text was updated successfully, but these errors were encountered: