mcp: simplify and fix the streamable client transport
Make several cleanups of the streamable client transport, encountered during work on JSON support for the streamable server: - The 'Close' condition is differentiated from asynchronous failures. A failure should unblock Read with an error, at which point the JSON-RPC connection will be broken and closed. - Fields are reordered in streamableClientConn to make guards more apparent. - The handling of sessionID is simplified: we simply set the session ID whenever we receive response headers. No need to have special handling for the first request, as the serializeation of session initialization is implemented in Client.Connect. - Since the above bullet makes Write a trivial wrapper around postMessage, the two methods are merged. - A bug is fixed where JSON responses were handled synchronously in Write. This lead to deadlock when a hanging client->server request is waiting on a server->client request. Now JSON is handled symmetrically to SSE: the Write returns once response headers are received. asynchronous to Write. - The httpConnection interface is renamed to clientConnection, and receive the entire InitializeResult. - streamableClientConn receivers are renamed to be consistently 'c'.
This commit is contained in:
parent
c03cd684ab
commit
6ea7a6c653
1 changed files with 167 additions and 140 deletions
|
|
@ -60,10 +60,11 @@ type Connection interface {
|
|||
SessionID() string
|
||||
}
|
||||
|
||||
// An httpConnection is a [Connection] that runs over HTTP.
|
||||
type httpConnection interface {
|
||||
// A clientConnection is a [Connection] that is specific to the MCP client, and
|
||||
// so may receive information about the client session.
|
||||
type clientConnection interface {
|
||||
Connection
|
||||
setProtocolVersion(string)
|
||||
initialized(*InitializeResult)
|
||||
}
|
||||
|
||||
// A StdioTransport is a [Transport] that communicates over stdin/stdout using
|
||||
|
|
|
|||
Loading…
Reference in a new issue