qft VS message-io

And another similar one tool is QFT which is pure p2p (the only embedded STUN used to find peers)

qft

I would use something like qft or croc for file transfers on an internal network, and not have those machines connected to the Internet (or have file transfers use only an internal/private network adapter/IP).

croc or qft or SimpleXChat.

croc or qft.

The git repo: https://github.com/tudbut/qft - The releases page has precompiled binaries for linux, mac, and windows.

message-io: a networking library meant to be very simple, built on mio.

Another one I know about, but have not looked into yet, is message-io.

I'm working in a transport network library that possible fits as a building block for yours and solves the problem of using different underlying transports: message-io

Here is benchmarks

I think https://github.com/lemunozm/message-io can be a good candidate.

The idea behind message-io is not to populate a current transport with a lot of options/profiles/modifications... this obfuscates the default way of working with it. Instead, if you want to build some behaviour on top of it, it is as easy as making an adapter! Following this pattern, you can split the way of using the library from the behaviour of the transport, keeping the things simple.

The initial purpose was to show the capabilities of https://github.com/lemunozm/message-io Nevertheless, Termchat is growing and needs to polish some of its features. At this point it is not for real-world use but I hope to reach this target.