Skip to content

should be allow specifying a DispatchQueue per registered item? #21

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

Closed
weissi opened this issue Apr 3, 2020 · 2 comments
Closed

should be allow specifying a DispatchQueue per registered item? #21

weissi opened this issue Apr 3, 2020 · 2 comments
Milestone

Comments

@weissi
Copy link
Collaborator

weissi commented Apr 3, 2020

Often, sub-systems won't be thread-safe so we rely on start & stop being called from the same thread. That is achievable with Configuration however only per Lifecycle and not once per item. What if two separate items rely on being each started/stopped on their own queue?

@weissi
Copy link
Collaborator Author

weissi commented Apr 3, 2020

Not sure if absolutely necessary but we should at least have an "API hole" to plug this in in a subsequent release.

@FranzBusch
Copy link
Contributor

Since we just changed the whole package to use a new Structured Concurrency approach, I would like to close this issue. @weissi Is that fine with you?

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

No branches or pull requests

3 participants