Obsolete/libipc-old
Archived
3
0
Fork 0
Code
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.
This repository has been archived on 2024-06-18. You can view files and clone it, but cannot push or open issues or pull requests.
460 Commits 4 Branches 0 Tags 1.1 MiB
Zig 37.1%
C 32.9%
Crystal 18.1%
Makefile 11.4%
Shell 0.5%
a6e1609fe6
Go to file
Philippe Pittoli a6e1609fe6 Readme: link to the new Zig implementation.
2023-02-05 06:00:30 +01:00
cat cat.zig: simplification. 2022-05-01 00:41:11 +02:00
docs Libipc presentation update. 2023-01-21 01:47:58 +01:00
examples fd-exchange tests in C: fix socket names. 2023-01-03 12:09:28 +01:00
man
src Fix socket options. 2023-01-03 12:10:08 +01:00
tests Fixed tests (3 and 4). 2022-02-04 03:22:26 +01:00
zig-impl Crystal bindings: remove useless 'puts'. 2023-02-04 10:30:10 +01:00
.gitignore Ignore presentation files. 2023-01-20 22:13:16 +01:00
Makefile
project.zsh
README.md Readme: link to the new Zig implementation. 2023-02-05 06:00:30 +01:00

README.md

OBSOLETED BY

This project was obsoleted by the new Zig implementation. Code is smaller, simpler and safer to use. Packet format and API are a bit simpler, too.

libipc

libipc - Simple, easy-to-use IPC library

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

See the presentation in docs/libipc.md.

Compilation

make

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 will be rewritten in Zig -- DONE!
  • 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 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