7f68ea5bc0Clients can now subscribe to specific resources and receive targeted notifications when those resources change. Previously, calling `notifyResourceUpdated` on the server would broadcast the notification to every connected client regardless of interest — now only sessions that have explicitly subscribed to a given resource URI receive the update, making resource change propagation both correct and efficient. The subscription lifecycle is fully handled: clients can subscribe and unsubscribe at any time, and the server cleans up subscription state when a session closes. Supersedes #838. Resolves #837, #776. --------- Signed-off-by: Dariusz Jędrzejczyk <dariusz.jedrzejczyk@broadcom.com>
13 lines
528 B
YAML
13 lines
528 B
YAML
# MCP Java SDK Conformance Test Baseline
|
|
# This file lists known failing scenarios that are expected to fail until fixed.
|
|
# See: https://github.com/modelcontextprotocol/conformance/blob/main/SDK_INTEGRATION.md
|
|
|
|
client:
|
|
# SSE retry field handling not implemented
|
|
# - Client does not parse or respect retry: field timing
|
|
# - Client does not send Last-Event-ID header
|
|
- sse-retry
|
|
# CIMD not implemented yet
|
|
- auth/basic-cimd
|
|
# Scope step up beyond initial authorization request not implemented
|
|
- auth/scope-step-up
|