OLD IMPLEMENTATION. The new one is in Zig and fucking ROCKS: https://git.baguette.netlib.re/Baguette/libipc Inter-Process Communication library based on unix sockets.

Go to file

Karchnu 282cc59c18 version bump		2020-07-12 22:00:18 +02:00
examples	lacking default cb_out	2020-07-08 12:40:24 +02:00
man	WIP	2020-06-27 19:16:07 +02:00
src	closing sockets (but not the client in a switch)	2020-07-12 20:35:55 +02:00
tests	s/events_loop/wait_event/	2020-07-06 08:43:06 +02:00
.gitignore	Meaningful error msg, -logging +directory management, indentation.	2020-01-01 12:11:34 +01:00
Makefile	WIP: no mem leaks on simple use. switch still to test.	2020-07-01 09:53:24 +02:00
README.md	version bump	2020-07-12 22:00:18 +02:00
project.zsh	version bump	2020-07-12 22:00:18 +02:00

README.md

libipc

libipc - Simple, easy-to-use IPC library

See the introductory man page.

Compilation

make

logging system

Logs are in one of the following directories: $XDG_DATA_HOME/ipc/ or $HOME/.local/share/ipc/. The log file can be indicated with the IPC_LOGFILE environment variable, too.

To remove logs: make LDFLAGS=-DIPC_WITHOUT_ERRORS

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

Planning for 0.9

libipc should use libevent for performance improvments
libipc should be thread-safe

Planning for 1.0

libipc may be written in Zig
libipc should have usable bindings in several languages

Implementation design

Memory management

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