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+
xadd has the NOMKSTREAM option.
- for Redis 5 and less the key idea is to combine one
exists call then monitor the keyspace for changes on the key.
We have at least two issues in the current RPC handling:
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.
xaddhas theNOMKSTREAMoption.existscall then monitor the keyspace for changes on the key.