Readme: less outdated stuff.
parent
7cb5d2669c
commit
c8757d0fb0
15
README.md
15
README.md
|
@ -3,20 +3,15 @@
|
|||
|
||||
libipc - Simple, easy-to-use IPC library
|
||||
|
||||
See the introductory [man page](man/libipc.7.md).
|
||||
See the introductory man page in `man/libipc.7`.
|
||||
|
||||
> This library is a work in progress, but is already used intensively in production.
|
||||
> It works, but we provide no warranty.
|
||||
|
||||
# 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
|
||||
|
@ -27,6 +22,7 @@ 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
|
||||
|
||||
|
@ -35,7 +31,6 @@ For performance improvements within `libipc`:
|
|||
|
||||
# Planning for 1.0
|
||||
|
||||
- `libipc` *may* be written in Zig
|
||||
- `libipc` should have usable bindings in several languages
|
||||
|
||||
|
||||
|
|
Reference in New Issue