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

Try using AsynchronousSocketChannel #282

Open
ForNeVeR opened this issue Jun 26, 2023 · 0 comments
Open

Try using AsynchronousSocketChannel #282

ForNeVeR opened this issue Jun 26, 2023 · 0 comments
Labels
kind:enhancement New feature or request kind:refactoring Changing the code without changing the user-visible behavior

Comments

@ForNeVeR
Copy link
Owner

Currently, our socket code uses blocking read calls on a separate thread.

This could be migrated to AsynchronousSocketChannel that's Future-based, and that would allow to make the code better, use fewer resources (no thread stack), and also maybe even fix the issues like #84.

@ForNeVeR ForNeVeR added kind:enhancement New feature or request kind:refactoring Changing the code without changing the user-visible behavior labels Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:enhancement New feature or request kind:refactoring Changing the code without changing the user-visible behavior
Projects
None yet
Development

No branches or pull requests

1 participant