This repository has been archived on 2024-06-18. You can view files and clone it, but cannot push or open issues/pull-requests.
2016-12-23 13:06:31 +01:00
|
|
|
|
2018-11-20 10:44:49 +01:00
|
|
|
# libipc
|
2017-01-01 18:48:06 +01:00
|
|
|
|
2018-11-20 10:44:49 +01:00
|
|
|
libipc - Simple, easy-to-use IPC library
|
2017-01-01 18:48:06 +01:00
|
|
|
|
2018-11-20 10:44:49 +01:00
|
|
|
See the introductory [man page](man/libipc.7.md).
|
2016-12-23 13:06:31 +01:00
|
|
|
|
2019-07-27 15:47:50 +02:00
|
|
|
# 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`
|
2020-07-03 22:27:56 +02:00
|
|
|
|
|
|
|
|
# Planning for 0.7
|
|
|
|
|
|
|
|
|
|
- `libipc` should have callbacks to use along with switching capabilities, making easier to implement proxies with communication protocols
|
|
|
|
|
|
|
|
|
|
# Planning for 0.8
|
|
|
|
|
|
|
|
|
|
- `libipc` should be thread-safe
|
|
|
|
|
|
|
|
|
|
# Planning for 0.8
|
|
|
|
|
|
|
|
|
|
- `libipc` should use `libevent` for performance improvments
|
|
|
|
|
|
|
|
|
|
# Planning for 1.0
|
|
|
|
|
|
|
|
|
|
- `libipc` should have usable bindings in several languages
|
2020-07-08 13:38:48 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
# Implementation design
|
|
|
|
|
|
|
|
|
|
## Memory management
|
|
|
|
|
|
|
|
|
|
1. Prefer stack over mallocs.
|
|
|
|
|
2. Basic functions (such as *usock_*) should not handle memory allocation.
|
