eCAL VS nanomsg

New version (5.94) of the high performance interprocess / interhost communication framework eCAL is available. eCAL supports different transport layer like shared memory for interprocess and udp multicast for interhost communication. It does not force the user to use a specific serialization format but supports some of the standards like google protobuf, capnproto or flatbuffers. The API is wrapped to C, C++, Python, C#, Rust and Go (the last two I never tested ;-)). Here you can find all the documentation. Check out the great applications for monitoring, record and replay. eCAL is Apache 2 licensed, repository hosted here. Have fun :-)

I you just need a fast publish / subscribe framework for windows you can give eCAL a try. The setup is done in less a minute and their is no dependency hell. Just to mention it as alternative. Documentation here

I would concider using eCAL since it blasts everything out of the water in terms of performance and comes with some handy tooling for inspection of messages in-travel.

Source on GitHub: https://github.com/continental/ecal

Check out eCal.

This really makes me want to try https://github.com/continental/ecal with https://github.com/google/flatbuffers to see how they compare. I also know that gpc for cpp at least stops functioning by about 4 MB of request size. Which I find stupid. What if I want to send uncompressed bitmaps!

Congratulations. Well done. eCAL will update as soon as possible to the new release. The new custom header and the n:m pub/sub support are really welcome new features.

Here is their counter callback example: https://github.com/continental/ecal/blob/master/samples/cpp/counter/counter_rec_cb/src/counter_rec_cb.cpp

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?