docs: document support for resumability and redelivery (#606)
Add missing documentation on resumability and redelivery in the streamable transport. Indirectly, also update stale transcluded examples. Example changes weren't causing CI failure as we only trigger the docs check on changes to the raw docs.
This commit is contained in:
parent
1a907bcd6f
commit
80abbe6171
1 changed files with 32 additions and 3 deletions
|
|
@ -112,6 +112,19 @@ client, err := mcp.Connect(ctx, transport, &mcp.ClientOptions{...})
|
|||
The `StreamableClientTransport` handles the HTTP requests and communicates with
|
||||
the server using the streamable transport protocol.
|
||||
|
||||
#### Resumability and Redelivery
|
||||
|
||||
By default, the streamable server does not support [resumability or
|
||||
redelivery](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#resumability-and-redelivery)
|
||||
of messages, because doing so requires either a persistent storage solution or
|
||||
unbounded memory usage (see also
|
||||
[#580](https://github.com/modelcontextprotocol/go-sdk/issues/580)).
|
||||
|
||||
To enable resumability, set `StreamableHTTPOptions.EventStore` to a non-nil
|
||||
value. The SDK provides a `MemoryEventStore` for testing or simple use cases;
|
||||
for production use it is generally advisable to use a more sophisticated
|
||||
implementation.
|
||||
|
||||
#### Stateless Mode
|
||||
|
||||
The streamable server supports a _stateless mode_ by setting
|
||||
|
|
|
|||
Loading…
Reference in a new issue