Re:Is it just me or is networking really hard?
by Const-me on Sunday September 13, 2015 @08:44PM
(#10213246)
You shouldn’t just compare C++ libraries. First, define your requirements, both functional (what should your networking do) and technical (latency, throughput, available bandwidth, operating systems of both clients and servers). Second, pick a protocols stack. Only then, look for those C++ libraries.
If on step #2 you’ll choose e.g. ProtoBuff + UDP, you’ll have totally different set of available libraries than if you choose SOAP + HTTPS. Besides, very few of those libraries work well on multiple platforms, e.g. libuv does, while libevent does not.
In addition, C++ is not the only choice. I once developed networking module for a game in C#. Have a few friends who are doing the same in finance industry.
So could the local experts give their opinion on C++ networking libraries? I know there are a few [1] but how do they compare?
I've only used Qt networking and POSIX sockets (although for C), but the application didn't have much of latency or throughput requirements.
[1] http://stackoverflow.com/questions/118945/best-c-c-network-l...