Skip to content
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

Need RCVPRIO and SNDPRIO options #104

Closed
gdamore opened this issue Oct 6, 2017 · 3 comments · May be fixed by #1743
Closed

Need RCVPRIO and SNDPRIO options #104

gdamore opened this issue Oct 6, 2017 · 3 comments · May be fixed by #1743
Milestone

Comments

@gdamore
Copy link
Contributor

gdamore commented Oct 6, 2017

For legacy compatibility, and perhaps for other use case, it would be nice to support tuning the
send and receive priorities. The send priority especially would be useful for REQ/REP when
dealing with "less optimal" peers (e.g. over a wider area network).

@gdamore gdamore added this to the v1.1 milestone Oct 7, 2018
@gdamore
Copy link
Contributor Author

gdamore commented Nov 6, 2018

This is a bigger change, and as much as I want it, I don't want to hold the v1.1 release for it; there is too much good stuff we still need.

@gdamore gdamore modified the milestones: v1.1, v1.2 Nov 6, 2018
@gdamore gdamore modified the milestones: v1.2, v1.4 Jan 21, 2020
@gdamore gdamore modified the milestones: v1.4, v1.5 Dec 29, 2020
muryliang pushed a commit to muryliang/nng that referenced this issue Mar 30, 2023
This converts this test to use something other than go convey.
It is the first conversion.  More will follow.
@hoytluo
Copy link

hoytluo commented Dec 16, 2023

Since it has reached to v1.6, what about this feature?

@gdamore
Copy link
Contributor Author

gdamore commented Jan 2, 2024

Duplicate of #11

@gdamore gdamore marked this as a duplicate of #11 Jan 2, 2024
@gdamore gdamore closed this as completed Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants