Repository navigation
Don't allow Redis RPC's client to add messages to streams that doesn't exists #148
Description
We have at least two issues in the current RPC handling:
- A client sending messages to a service that doesn't exist.
- A client sending messages to a method that isn't implemented.
Although the client (per spec) will eventually timeout and the correctness of the application will be maintained, this will leave garbage in Redis.
We should implement a way to prevent the RPC client from adding messages in these two cases.
- In Redis 6.2+
xaddhas theNOMKSTREAMoption. - for Redis 5 and less the key idea is to combine one
existscall then monitor the keyspace for changes on the key.
Activity