RediStack
RediStack copied to clipboard
swift-server
Non-blocking, event-driven Swift client for Redis.
The old subscription is silently dropped.
If a user has multiple paths in the same codebase that subscribe to the same channel, we could merge those calls into a single subscription. That would be more efficient...
Concurrency is increasingly a critical part of the Swift ecosystem, even more so on Server than other Swift ecosystems. RediStack doesn't currently support concurrency at all, and users are manually...
In #122 I mentioned that the performance of RESP is not great. There is a successor in the RESP3 module that is much more performance oriented though. While RESP3 is...
Redis is commonly used in scenarios where performance and throughput matter. The currently used RESP implementation is measurably slow.
`onUnsubscribe` is currently only called when a subscription is _formally_ cancelled by the user. If a socket error closes the connection, the subscription isn't alive anymore, but because `onUnsubscribe` isn't...
RediStack currently doesn't allow users to connect over TLS. This is an increasingly common requirement.
Fix zpop commands. They have been set to read the first value as the score when it is the second value. See https://redis.io/docs/latest/commands/zpopmin/ for reference I also fixed the bzpop...
We no longer have the swift-server jenkins and have to adopt github actions.
Metadata
Owner
Metadata
Non-blocking, event-driven Swift client for Redis.