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

Delegate thread management to I/O framework #26

Closed
flowersinthesand opened this issue Jun 12, 2018 · 0 comments
Closed

Delegate thread management to I/O framework #26

flowersinthesand opened this issue Jun 12, 2018 · 0 comments
Assignees
Milestone

Comments

@flowersinthesand
Copy link
Member

@flowersinthesand flowersinthesand commented Jun 12, 2018

According to the design philosophy, Asity shouldn't get involved in thread management to enable end users to have a full control of framework they use. However, some bridges now create and run a thread for some reason.

At least, they should delegate thread management to underlying I/O framework by submitting a task to the I/O framework's thread pool.

@flowersinthesand flowersinthesand added this to the 2.0.0-Beta1 milestone Jun 12, 2018
@flowersinthesand flowersinthesand self-assigned this Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant