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

Consider removing wt.datagrams.writable #624

Open
jan-ivar opened this issue Dec 4, 2024 · 4 comments
Open

Consider removing wt.datagrams.writable #624

jan-ivar opened this issue Dec 4, 2024 · 4 comments
Labels
Discuss at next meeting Flags an issue to be discussed at the next WG working

Comments

@jan-ivar
Copy link
Member

jan-ivar commented Dec 4, 2024

No description provided.

@martenrichter
Copy link

And what would be the replacement? A single sending method?
Would readable also be replaced? ( I am just curious, as I want to keep the interface up to date).

@jan-ivar
Copy link
Member Author

jan-ivar commented Dec 5, 2024

Sorry I created this in a meeting with insufficient description. This would be after #620 is merged.

There would still be a single readable for incoming datagrams.

@vasilvv
Copy link
Contributor

vasilvv commented Dec 10, 2024

I feel like it's worth keeping the default writable, since most applications would only need one.

@wilaw wilaw added the Discuss at next meeting Flags an issue to be discussed at the next WG working label Dec 17, 2024
@jan-ivar
Copy link
Member Author

Meeting:

  • leaning toward keeping.
  • what should the default sendOrder for wt.datagrams.writable be? 1 or max int?
  • If you don't want the wt.datagrams.writable to starve everything else you need to put stuff in a different send group.

@jan-ivar jan-ivar added Ready for PR and removed Discuss at next meeting Flags an issue to be discussed at the next WG working labels Dec 17, 2024
@wilaw wilaw added this to the Candidate Recommendation milestone Feb 12, 2025
@wilaw wilaw added Discuss at next meeting Flags an issue to be discussed at the next WG working and removed Ready for PR labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discuss at next meeting Flags an issue to be discussed at the next WG working
Projects
None yet
Development

No branches or pull requests

4 participants