Inter-Process Communication library based on unix sockets.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Philippe Pittoli 13e7619899 Fixed tests (3 and 4). 8 months ago
docs Better presentation, for the ones only reading it online. 2 years ago
examples Minor changes in examples. 2 years ago
man Man page added. 2 years ago
src Wrong pointer read. 8 months ago
tests Fixed tests (3 and 4). 8 months ago
.gitignore Meaningful error msg, -logging +directory management, indentation. 3 years ago
Makefile v0.7.2: ipcd indicates if it successfully contacted the service. 2 years ago Readme fix. 2 years ago
project.zsh v0.7.2: ipcd indicates if it successfully contacted the service. 2 years ago


libipc - Simple, easy-to-use IPC library

See the introductory man page in man/libipc.7.

See the presentation in docs/

This library is a work in progress, but is already used intensively in production. It works, but we provide no warranty.



Since 0.7

  • libipc have callbacks to use along with switching capabilities, making easier to implement proxies for different communication protocols

Planning for 0.8

For performance improvements within libipc:

  • libipc shouldn't use realloc for each event (new client, new message, etc.) but by batch of a few thousand elements
  • libipc should use better internal structures, unrequiring the use of loops (over the whole list of messages or connections) for each action
  • libipc will be rewritten in Zig

Planning for 0.9

  • libipc should use epoll/kqueue for performance improvments
    • new functions will be added to the API
    • but we'll keep the same API for applications with no need for threading (way simpler implementation)
  • libipc should be thread-safe

Planning for 1.0

  • libipc should have usable bindings in several languages

Implementation design

Memory management

  1. Prefer stack over mallocs.
  2. Basic functions (such as usock_) should not handle memory allocation.