docs: server-assisted CSC and CLIENT TRACKINGINFO (Python, Node, Go, C#) - #285
Open
Aryex wants to merge 2 commits into
Open
docs: server-assisted CSC and CLIENT TRACKINGINFO (Python, Node, Go, C#)#285Aryex wants to merge 2 commits into
Aryex wants to merge 2 commits into
Conversation
Aryex
changed the title
Collaborator
Author
|
📝 Updated PR description with |
Aryex
added
AI Generated
documentation
Aryex
force-pushed
the
alexl/agent/csc-server-assisted-trackinginfo
branch
from
July 26, 2026 21:27
2e51e60 to
72d1585
Compare
…e, Go Signed-off-by: kiro-agent <kiro-agent@users.noreply.github.com>
Signed-off-by: kiro-agent <kiro-agent@users.noreply.github.com>
Aryex
force-pushed
the
alexl/agent/csc-server-assisted-trackinginfo
branch
from
July 27, 2026 14:37
72d1585 to
7a29729
Compare
Aryex
marked this pull request as ready for review
July 27, 2026 14:37
Aryex
requested review from
affonsov and
xShinnRyuu
and removed request for
currantw
July 27, 2026 14:38
jeremyprime
reviewed
Jul 27, 2026
| cache := config.NewClientSideCache(1024, 60000). | ||
| WithServerAssisted(true) // Enable server-assisted invalidation | ||
|
|
||
| clientConfig := config.NewGlideClientConfiguration(). |
Collaborator
There was a problem hiding this comment.
Should be config.NewClientConfiguration().
jeremyprime
reviewed
Jul 27, 2026
| clientConfig := config.NewGlideClientConfiguration(). | ||
| WithAddress(&config.NodeAddress{Host: "localhost", Port: 6379}). | ||
| WithClientSideCache(cache) | ||
| client, err := glide.NewGlideClient(clientConfig) |
Collaborator
There was a problem hiding this comment.
Should be glide.NewClient(clientConfig).
affonsov
reviewed
Jul 29, 2026
|
|
||
| <Aside type="caution" title="TTL-Only Caching (Default)"> | ||
| By default, client-side caching uses **TTL-based expiration only**. Cached entries may become stale before their TTL expires if **any client** modifies the underlying data, **including the same client that cached the value**. A read issued immediately after the same client's `SET` / `HSET` / `SADD` / `DEL` will still return the cached value until its TTL expires. **Java** now supports [server-assisted invalidation](#server-assisted-invalidation) via the [`CLIENT TRACKING`](https://valkey.io/commands/client-tracking/) protocol, which pushes invalidation messages from the server when keys change. Other languages still use TTL-only mode; server-assisted support will be added in future releases. | ||
| By default, client-side caching uses **TTL-based expiration only**. Cached entries may become stale before their TTL expires if **any client** modifies the underlying data, **including the same client that cached the value**. A read issued immediately after the same client's `SET` / `HSET` / `SADD` / `DEL` will still return the cached value until its TTL expires. **Java, Python, Node.js, and Go** now support [server-assisted invalidation](#server-assisted-invalidation) via the [`CLIENT TRACKING`](https://valkey.io/commands/client-tracking/) protocol, which pushes invalidation messages from the server when keys change. PHP still uses TTL-only mode; server-assisted support will be added in a future release. |
Collaborator
There was a problem hiding this comment.
Suggested change
| By default, client-side caching uses **TTL-based expiration only**. Cached entries may become stale before their TTL expires if **any client** modifies the underlying data, **including the same client that cached the value**. A read issued immediately after the same client's `SET` / `HSET` / `SADD` / `DEL` will still return the cached value until its TTL expires. **Java, Python, Node.js, and Go** now support [server-assisted invalidation](#server-assisted-invalidation) via the [`CLIENT TRACKING`](https://valkey.io/commands/client-tracking/) protocol, which pushes invalidation messages from the server when keys change. PHP still uses TTL-only mode; server-assisted support will be added in a future release. | |
| By default, client-side caching uses **TTL-based expiration only**. Cached entries may become stale before their TTL expires if **any client** modifies the underlying data, **including the same client that cached the value**. A read issued immediately after the same client's `SET` / `HSET` / `SADD` / `DEL` will still return the cached value until its TTL expires. **Java, Python, Node.js, and Go** now support [server-assisted invalidation](#server-assisted-invalidation) via the [`CLIENT TRACKING`](https://valkey.io/commands/client-tracking/) protocol, which pushes invalidation messages from the server when keys change. PHP and Csharp still uses TTL-only mode; server-assisted support will be added in a future release. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document server-assisted client-side caching (
serverAssistedconfig) andCLIENT TRACKINGINFOcommand for Python, Node.js, Go, and C# clients.Source Commits
5d936c6— Client-side caching: addserverAssistedconfig andCLIENT TRACKINGINFOcommand (Node, Python, Go, Java) (#6344)e70873a— AddserverAssistedclient-side caching config andCLIENT TRACKINGINFOcommand (C#) (C# #451)Changes
available-commands.json: changed C# status for CLIENT TRACKING and CLIENT TRACKINGINFO fromnot_availabletoavailable; removed csharp-href issue linksclient-side-caching.mdx: replaced "Not yet available" placeholders with real C# code examples in both the "Enabling server-assisted mode" and "CLIENT TRACKINGINFO" sectionsContext
valkey-glide #6344 implemented client-side caching phase 2 across Java, Python, Node.js, and Go. valkey-glide-csharp #451 brings the same feature to C#:
ClientSideCacheConfig.WithServerAssisted(true)enables server-assisted invalidation viaCLIENT TRACKING ON BCAST, andClientTrackingInfoAsync()exposes the diagnostic command on both standalone and cluster clients. Only PHP remains without server-assisted support.cc @currantw
This PR was generated by the automated documentation pipeline.