Clarify whether Lettuce should be listed as supporting client-side caching

[jspark-gif]

On the client-side caching page, the supported client libraries are currently listed as:

• redis-py
• Jedis
• node-redis

Source:
https://redis.io/docs/latest/develop/clients/client-side-caching/#which-client-libraries-support-client-side-caching

However, Lettuce’s official reference says support for CLIENT TRACKING was added:

https://redis.github.io/lettuce/new-features/

This makes it unclear whether:

1. Lettuce supports Redis client-side caching and should be included in the supported client list, or
2. CLIENT TRACKING support in Lettuce is not sufficient to qualify as documented CSC support in Redis docs.

Could you clarify the distinction? If Lettuce supports CSC in the same sense as the listed clients, it may need to be added. Otherwise, it would help to document why it is excluded.

[andy-stark-redis]

@jspark-gif Hi! Yeah, the distinction is that CLIENT TRACKING simply enables/disables and configures the features needed to support CSC on the server side. Supporting CSC in the client code requires other features that aren't implemented in Lettuce yet.

I've made a PR to clarify this distinction on the CSC page. This should get approved and merged shortly and will get published in the docs, probably within a day or so.

Thanks very much for spotting this!