nanomsg
nanomsg library (by nanomsg)
rpclib
rpclib is a modern C++ msgpack-RPC server and client library (by rpclib)
Our great sponsors
nanomsg | rpclib | |
---|---|---|
1 | 4 | |
5,857 | 1,598 | |
0.5% | 0.0% | |
6.3 | 0.0 | |
3 months ago | over 1 year ago | |
C | C++ | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nanomsg
Posts with mentions or reviews of nanomsg.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Question on cross platform libraries and networking
I've had a look at some open source libraries that already support networking on different platforms like nanomsg, but I can't really tell how the library includes it's headers. My current idea is to use the processors to include the right headers for each system, and then each function would do the same. In a makefile I would do the same for linking correctly. Is this a good method, or is there an easier way? Or does it not matter overall as long as the library works?
rpclib
Posts with mentions or reviews of rpclib.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-04-24.
-
Is there a way to keep the client alive in rpclib?
If by rpclib you mean this: https://github.com/rpclib/rpclib then it's not clear what you're talking about. The code for that client retains the connection to the server for the duration of the connection, though of course if you simply wait for too long without sending anything the connection will time out and get torn down.
-
rpclib is looking for a new maintainer
Thanks for all your hard work in the past years. I'm not able to take over as a maintainer, but you mentioned CI rot and I can take thorough look at that! I opened a small PR refactoring the AppVeyor configuration.
What are some alternatives?
When comparing nanomsg and rpclib you can also consider the following projects:
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
Apache Thrift - Apache Thrift
eCAL - Please visit the new repository: https://github.com/eclipse-ecal/ecal
simple-rpc-cpp - a simple RPC wrapper generator to C/C++ functions