-
-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Add RDS_CMSG_RXPATH_LATENCY
to socket
#127383
Comments
RDS_CMSG_RXPATH_LATENCY
to socket
Both the devguide and the issue template instructs you to explain what you are proposing and why you are proposing it. The sentence above does neither of those. Yes, I know this is a trivial issue, but that's no excuse for dismissing our workflow. Why are you proposing to add |
Ask yourself these questions every time you propose a new feature, even if it is just a flag to some syscall wrapper. |
Thank you for your guidance, I'll do better next time. I modified it and added the description of another PR. |
Read again what I already explained: #127383 (comment) |
Please explain how the constant can be used from a Python perspective using the |
I changed the example to a Python-like form, which seems to be more expressive and more suitable for the Python community. |
Feature or enhancement
Proposal:
This issue suggests adding new RDS constants.
It‘s used to query the
rx-path
(that's receive) latency of RDS. Usually used to optimize RDS communication, such as controlling the number of connections and other strategiesHas this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs
RDS_CMSG_RXPATH_LATENCY
tosocket
#127384The text was updated successfully, but these errors were encountered: