liuyf5231 / yail

An IPC library that implements publish/subscribe (PUBSUB) and remote procedure call (RPC) functionality.

YAIL: Yet Another IPC Library

YAIL is a C++ library that provides publish/subscribe (PUBSUB) and remote procedure call (RPC) functionality with a strongly typed templated API.

The PUBSUB functionality is based on concepts from Data Distribution Service (DDS) standard from Object Management Group (OMG). YAIL separates the IPC messaging layer from the underlying transport enabling user to instantiate YAIL pubsub or rpc service with specific transport at compile time.

PUBSUB

YAIL library currently provides following transports for PUBSUB service:

• UDP multicast
• Shared Memory

RPC

YAIL library currently provides following transports for RPC service:

• UNIX Domain

Dependencies

YAIL depends on following libraries:

• Standard C++
• Boost ASIO
• Google protobuf
• Boost Interprocess (only if shared memory transport is enabled)
• POSIX threads (only if shared memory transport is enabled)

Build and Installation

$ cd ~/projects
$ git clone git://github.com/agrewal707/yail.git
$ mkdir -p build/yail
$ cd build/yail
$ cmake -DYAIL_PUBSUB_ENABLE_UDP_TRANSPORT=on -DCMAKE_INSTALL_PREFIX=local -DCMAKE_BUILD_TYPE=MinSizeRel ../../yail
$ make install/strip

Tests

$ sudo LD_LIBRARY_PATH=local/lib make test
Running tests...
Test project /home/agrewal/projects/build/yail
      Start  1: pubsub_udp_async_singlethreaded
 1/12 Test  #1: pubsub_udp_async_singlethreaded ................   Passed    5.05 sec
      Start  2: pubsub_udp_sync_multithreaded
 2/12 Test  #2: pubsub_udp_sync_multithreaded ..................   Passed    8.03 sec
      Start  3: pubsub_shmem_async_singlethreaded
 3/12 Test  #3: pubsub_shmem_async_singlethreaded ..............   Passed    5.37 sec
      Start  4: pubsub_shmem_sync_multithreaded
 4/12 Test  #4: pubsub_shmem_sync_multithreaded ................   Passed    8.44 sec
      Start  5: rpc_unix_domain_sync_call_reply_ok
 5/12 Test  #5: rpc_unix_domain_sync_call_reply_ok .............   Passed    1.05 sec
      Start  6: rpc_unix_domain_async_call_reply_ok
 6/12 Test  #6: rpc_unix_domain_async_call_reply_ok ............   Passed    1.04 sec
      Start  7: rpc_unix_domain_sync_call_reply_delayed
 7/12 Test  #7: rpc_unix_domain_sync_call_reply_delayed ........   Passed    5.04 sec
      Start  8: rpc_unix_domain_async_call_reply_delayed
 8/12 Test  #8: rpc_unix_domain_async_call_reply_delayed .......   Passed    2.04 sec
      Start  9: rpc_unix_domain_sync_call_reply_error
 9/12 Test  #9: rpc_unix_domain_sync_call_reply_error ..........   Passed    1.05 sec
      Start 10: rpc_unix_domain_async_call_reply_error
10/12 Test #10: rpc_unix_domain_async_call_reply_error .........   Passed    1.04 sec
      Start 11: rpc_unix_domain_sync_call_timeout_reply_ok
11/12 Test #11: rpc_unix_domain_sync_call_timeout_reply_ok .....   Passed    1.04 sec
      Start 12: rpc_unix_domain_sync_call_timeout_reply_none
12/12 Test #12: rpc_unix_domain_sync_call_timeout_reply_none ...   Passed    4.04 sec

100% tests passed, 0 tests failed out of 12

Total Test time (real) =  43.24 sec

Documentation

$ make doc