From f80d10b8dea9035fdae94f5541481e3a388f98bb Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Sat, 21 Oct 2017 23:59:27 +0200 Subject: Update readme MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- README | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README b/README index beb3393..d5f624c 100644 --- a/README +++ b/README @@ -4,6 +4,9 @@ Features: Support for multi-user buses. No support state-keeping in clients. Supports all send(2)/recv(2) flags. + Almost full setsockopt(2)/getsockopt(2)/fcntl(2)/ioctl(2) support: + No send-time timestamps + Increasing message size limit may cause problems Support for routing keys with wildcards. Non-features: @@ -13,6 +16,9 @@ Non-features: No support for automatic unsubscriptions. No support for reply-to keys, should be implemented at application level. No support for shared queues, should be implemented as a separate service. + No file descriptor passing support, not network-compatible, should be + implemented as a separate service or at application level. + No support for server-verified credentials, not network-compatible Routing keys: Routing keys are used to filter received messages. A routing key @@ -23,7 +29,8 @@ Routing keys: pattern ends with '.' that '.' will match to a '.' and any subsequent byte. For example 'a.*.c.' will match 'a.b.c.' and 'a.b.c.d.e' but not 'a.b.c' or 'a.c.d'. And empty routiung key - pattern shall match everything. + pattern shall match everything. Routing keys starting with '!' + are reserved. Protocol: Communication is done over unix domain, sequenced-packet sockets. -- cgit v1.2.3-70-g09d2