Replies: 4 comments 1 reply
|
I'm happy to contribute this change, if you are willing to accept it |
0 replies
|
Many thanks! I am cleaning and fixing old code right now, hope to make it available in a few days. Seems like the perfect spot to test your suggestion, and all help is most welcome! |
1 reply
|
Ok, got initial PR here, have a look when you can :) Thanks! |
0 replies
|
PR is working and ready! :) closing this discussion |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've got a suggestion to drop Network and use Swift-NIO for connection.
Swift-NIO is an asynchronous event-driven network application framework.
Initialization: The connection is established using a ClientBootstrap and a MultiThreadedEventLoopGroup.
Sending Data: Data sending is managed using ByteBuffers and the writeAndFlush method.
Receiving Data: Data reception is handled with a custom ByteToMessageDecoder to process incoming data.
Connection Lifecycle: The connection start and stop methods are adjusted for handling with Swift-NIO’s asynchronous patterns.
This focuses on integrating Swift-NIO effectively while preserving the logic and flow of your original application.
Here’s refactored the IBConnection and IBClient classes to use Swift-NIO:
All reactions