nanomsg / cppnanomsg

C++ binding for nanomsg

Welcome to nanomsg

The nanomsg library is a simple high-performance implementation of several "scalability protocols". These scalability protocols are light-weight messaging protocols which can be used to solve a number of very common messaging patterns, such as request/reply, publish/subscribe, surveyor/respondent, and so forth. These protocols can run over a variety of transports such as TCP, UNIX sockets, and even WebSocket.

For more information check the website.

Prerequisites

1. Windows.

   • Windows Vista or newer (Windows XP and 2003 are NOT supported)
   • Microsoft Visual Studio 2010 (including C++) or newer, or mingw-w64. (Specifically mingw and older Microsoft compilers are NOT supported, and we do not test mingw-w64 at all, so YMMV.)
   • CMake 2.8.12 or newer, available in $PATH as cmake

2. POSIX (Linux, MacOS X, UNIX)

   • ANSI C compiler supporting C89
   • POSIX pthreads (should be present on all modern POSIX systems)
   • BSD sockets support for both TCP and UNIX domain sockets
   • CMake (http://cmake.org) 2.8.12 or newer, available in $PATH as cmake

3. Documentation (optional)

   • asciidoctor (http://asciidoctor.org/) available as asciidoctor
   • If not present, docs are not formatted, but left in readable ASCII
   • Available on-line at http://nanomsg.org/documentation

Quick Build Instructions

These steps here are the minimum steps to get a default Debug build. Using CMake you can do many other things, including setting additional variables, setting up for static builds, or generation project or solution files for different development environments. Please check the CMake website for all the various options that CMake supports.

POSIX

This assumes you have a shell in the project directory, and have the cmake and suitable compilers (and any required supporting tools like linkers or archivers) on your path.

1. % mkdir build
2. % cd build
3. % cmake ..
4. % cmake --build .
5. % ctest .
6. % sudo cmake --build . --target install
7. % sudo ldconfig (if on Linux)

Windows

This assumes you are in a command or powershell window and have the appropriate variables setup to support Visual Studio, typically by running vcvarsall.bat or similar with the appropriate argument(s). It also assumes you are in the project directory.

1. md build
2. cd build
3. cmake ..
4. cmake --build . --config Debug
5. ctest -C Debug .
6. cmake --build . --config Debug --target install NB: This may have to be done using an Administrator account.

Alternatively, you can build and install nanomsg using vcpkg dependency manager:

1. git clone https://github.com/Microsoft/vcpkg.git
2. cd vcpkg
3. ./bootstrap-vcpkg.bat
4. ./vcpkg integrate install
5. ./vcpkg install nanomsg

The nanomsg port in vcpkg is kept up to date by microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.

Static Library

We normally build a dynamic library (.so or .DLL) by default.

If you want a static library (.a or .LIB), configure by passing -DNN_STATIC_LIB=ON to the first cmake command.

POSIX

POSIX systems will need to link with the libraries normally used when building network applications. For some systems this might mean -lnsl or -lsocket.

Windows

You will also need to define NN_STATIC_LIB in your compilation environment when building programs that use this library. This is required because of the way Windows changes symbol names depending on whether the symbols should be exported in a DLL or not.

When using the .LIB on Windows, you will also need to link with the ws2_32, mswsock, and advapi32 libraries, as nanomsg depends on them.

Support

This library is considered to be in "sustaining" mode, which means that new feature development has ended, and bug fixes are made only when strictly necessary for severe issues.

New development is now occurring in the NNG project, which offers both protocol and API compatibility with this project. Please consider using NNG for new projects.

Please see the file SUPPORT for more details.

cppnanomsg's Issues

atcp.c abort on Windows Platform

My application is running on Windows Platform and Linux Platform at the same time with Pair Mode, the windows platform is running with bind and linux with connect. After few hours, the application running on Windows abort with this error : (Unexpected action: state=2 source=1 action=5 (e:\workspace\nanomsg-1.1.4\src\transports\tcp\atcp.c:228).

The socket shutdown always gives EINVAL

Hi:
I am trying to make a proof-of-concept RPC with nanomsg and google protobuf.
The shutdown always gives EINVAL, what am I doing wrong ?

Example:
https://github.com/sroycode/nanorpc/blob/master/EchoClient.cc
line no 50 (commented out)

Exception thrown on recv if survey timed out

Submitting this as an issue, otherwise it gets lost on the mailinglist:
http://www.freelists.org/post/nanomsg/cppnanomsg-throws-on-recv-if-survey-timed-out

• recv throws except for EAGAIN
• should also allow error codes such as ETIMEDOUT, EFSM

The wrapper is not usable for the survey pattern, as it returns EFSM right now (should be ETIMEDOUT, see: nanomsg/nanomsg#194).

There's only a single exception type. Catching it on deadline expiration may also catch a fatal error.
There's no way to distinguish between them.

Tag releases of C++ bindings

Hi,

I think that it would be helpful to manage dependencies if we tag releases.

Cheers!

build cppnanomsg on win10-64,gcc has a problem

try to build cppnanomsg in win10-64 + codeblocks + cmake/win + mingw-gcc
from: https://nuwen.net/mingw.html
nanomsg itself built well.
cmake/win success, but when i try to build cppnanomsg i get: compiler problem:

#include <nanomsg/nn.h>
the file is in: C:\nanomsg-1.1.4\src

||=== Build: all in cppnanomsg (compiler: GNU GCC Compiler) ===|
C:\cppnanomsg-master\nn.hpp|26|fatal error: nanomsg/nn.h: No such file or directory|
[CMakeFiles\binding.dir\build.make|62|CMakeFiles/binding.dir/binding.cpp.obj] Error 1|
[CMakeFiles\Makefile2|72|CMakeFiles/binding.dir/all] Error 2|
[C:\cppnanomsg-master\build\Makefile|140|all] Error 2|
||=== Build failed: 4 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|