-
Notifications
You must be signed in to change notification settings - Fork 342
doc: Updates to nrf_modem. socket header files, and socket documentation #1904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
doc: Updates to nrf_modem. socket header files, and socket documentation #1904
Conversation
5f12e63 to
dd78e8c
Compare
kacperradoszewski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since NRF_SO_SENDCB is mentioned here already, maybe we should wait until #1897 is merged
dd78e8c to
758b8f9
Compare
| This flag is only supported for the :c:func:`nrf_send` and :c:func:`nrf_sendto` functions. | ||
| When this flag is used, the operation is blocked until the data has been acknowledged by the peer, if required by the network protocol, or until the timeout, given by the :c:macro:`NRF_SO_SNDTIMEO` socket option, is reached. | ||
| The valid timeout values are 1 to 600 seconds. | ||
| For TCP, the operation is blocked until the data is acknowledged by the peer, and for UDP, until the data is sent on-air by the modem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better to refer to stream and datagram sockets instead of TCP and UDP, which are protocols.
There are more protocols for which this flag applies, but the socket types (stream, datagram) actually cover the behavior in all cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated as below. Please check:
For the :c:macro:
NRF_SOCK_STREAMsocket type , the operation is blocked until the data is acknowledged by the peer, and for the :c:macro:NRF_SOCK_DGRAMsocket type, until the data is sent on-air by the modem.
| When this flag is used, the operation is blocked until the data has been acknowledged by the peer, if required by the network protocol, or until the timeout, given by the :c:macro:`NRF_SO_SNDTIMEO` socket option, is reached. | ||
| The valid timeout values are 1 to 600 seconds. | ||
| For TCP, the operation is blocked until the data is acknowledged by the peer, and for UDP, until the data is sent on-air by the modem. | ||
| This flag is useful in scenarios where data integrity and confirmation of receipt are critical. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This flag has no effect on data integrity, only when the user needs confirmation that the data has been sent and, if supported by the protocol, confirmation that it has been received.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated as below:
This flag is useful in scenarios where confirmation of receipt is critical.
| * :c:macro:`NRF_MSG_WAITACK` | ||
| Requests a blocking send operation until the request is acknowledged. | ||
| This flag is only supported for the :c:func:`nrf_send` and :c:func:`nrf_sendto` functions. | ||
| When this flag is used, the operation is blocked until the data has been acknowledged by the peer, if required by the network protocol, or until the timeout, given by the :c:macro:`NRF_SO_SNDTIMEO` socket option, is reached. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not very accurate. It could also be merged with the part below. What about:
When this flag is used, write operations on datagram sockets block until the data has been sent on air, and write operations on stream sockets block until data reception is acknowledged by the peer. The operation timeout can be configured using the ... socket option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated as below:
When this flag is used, write operations on datagram sockets are blocked until the data has been sent on air, and write operations on stream sockets are blocked until data reception is acknowledged by the peer.
The operation timeout can be configured using the :c:macro:NRF_SO_SNDTIMEOsocket option.
cc: @kacperradoszewski .
Updates to nrf_modem and socket header files to improve modem library "limits" documentation Signed-off-by: divya pillai <[email protected]>
758b8f9 to
3427028
Compare
Add section for Supported flags for socket functions Signed-off-by: divya pillai <[email protected]>
3427028 to
752f111
Compare
|



Updates to nrf_modem and socket header files
to improve modem library "limits" documentation.
Added Supported flags for socket functions section.
NCSDK-35090 and NCSDK-34607