Create a resource-free semantic view over a caller-owned node-redis client.
Read signals are passed to node-redis so queued commands can be removed when
supported. Aborting after dispatch does not unsend a command or prove the
server stopped executing it. Every write is one native SET of a complete
client-stamped frame. Invalidation retries any EVALSHA rejection once by
re-sending the script source as EVAL — the script is idempotent, so a
duplicate run is harmless — and a failed retry surfaces unmodified. An
accepted reply is validated after dispatch and is never retried. node-redis
has no per-command deadline:
disableOfflineQueue, commandsQueueMaxLength, and reconnectStrategy
bound queueing and dispatch, not the reply wait, so with the offline queue
enabled a retry issued during a disconnect can wait until reconnect. The
caller remains responsible for finite native command budgets, draining
work, and closing the client.
Create a resource-free semantic view over a caller-owned node-redis client. Read signals are passed to node-redis so queued commands can be removed when supported. Aborting after dispatch does not unsend a command or prove the server stopped executing it. Every write is one native SET of a complete client-stamped frame. Invalidation retries any EVALSHA rejection once by re-sending the script source as EVAL — the script is idempotent, so a duplicate run is harmless — and a failed retry surfaces unmodified. An accepted reply is validated after dispatch and is never retried. node-redis has no per-command deadline:
disableOfflineQueue,commandsQueueMaxLength, andreconnectStrategybound queueing and dispatch, not the reply wait, so with the offline queue enabled a retry issued during a disconnect can wait until reconnect. The caller remains responsible for finite native command budgets, draining work, and closing the client.