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.

Sign up for GitHub

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

Jump to bottom

Allow enabling/disabling IPv4 / 6 #8

Open
willstott101 opened this issue Apr 14, 2020 · 3 comments
Open

Allow enabling/disabling IPv4 / 6 #8

willstott101 opened this issue Apr 14, 2020 · 3 comments
Labels
enhancement New feature or request

Comments

@willstott101
Copy link
Contributor

per-Responder or per-Service ?

Inspired by #3
@willstott101
Copy link
Contributor Author

@ryanpresciense Have you got a real use-case for this?

@willstott101 willstott101 added the enhancement New feature or request label Apr 14, 2020
@willstott101 willstott101 mentioned this issue Apr 17, 2020
Closed
@ashthespy
Copy link
Member

One usecase for this might be - librespot-org/librespot#67

@willstott101
Copy link
Contributor Author

Interesting... perhaps making it possible to allow failure to bind to one of the two interfaces, would be enough.

Perhaps:

  • let responder = Responder::new()
  • responder.register(...) Can be before or after ipv4/6 binding
  • handle.spawn(responder.ipv4_task()?)
  • handle.spawn(responder.ipv6_task()?)

User-code can then decide to let things slide or not.

@ashthespy ashthespy mentioned this issue Nov 2, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@willstott101 @ashthespy