Following up on PR #1623 (SEP-2549 caching hints).
SEP-2549 lets servers advertise a non-zero ttlMs (and a cacheScope of public/private) on list/read results. The client currently surfaces these values (via the raw overloads) but does not act on them.
We could add optional client-side caching that:
- Caches list/read results keyed by request and serves them until the advertised TTL expires.
- Honors
cacheScope semantics (private results not shared beyond the current session/consumer; public potentially shareable).
- Handles invalidation, concurrency/thread-safety, and interaction with the existing tool cache.
This is effectively a new opt-in subsystem and should be designed/reviewed separately from the wire-format conformance work in PR #1623.
Following up on PR #1623 (SEP-2549 caching hints).
SEP-2549 lets servers advertise a non-zero
ttlMs(and acacheScopeofpublic/private) on list/read results. The client currently surfaces these values (via the raw overloads) but does not act on them.We could add optional client-side caching that:
cacheScopesemantics (privateresults not shared beyond the current session/consumer;publicpotentially shareable).This is effectively a new opt-in subsystem and should be designed/reviewed separately from the wire-format conformance work in PR #1623.