Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/protocol/v2/draft/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ The protocol follows the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) s
Unlike base JSON-RPC, request IDs **MUST** be a string or an integer, never
`null`. An error response has `id: null` only when the request ID could not be
determined.
A receiver rejects a message that has a `method` and an `id` of `null` with `-32600` (Invalid request) and `id: null`. It does not treat the message as a notification.

Both sides send requests, and each side chooses IDs for its own requests independently, so the same ID can be in use in both directions. A sender **MUST NOT** reuse an ID while a request with that ID is still awaiting a response.

Expand Down
1 change: 1 addition & 0 deletions docs/protocol/v2/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ The protocol follows the [JSON-RPC 2.0](https://www.jsonrpc.org/specification) s
Unlike base JSON-RPC, request IDs **MUST** be a string or an integer, never
`null`. An error response has `id: null` only when the request ID could not be
determined.
A receiver rejects a message that has a `method` and an `id` of `null` with `-32600` (Invalid request) and `id: null`. It does not treat the message as a notification.

Both sides send requests, and each side chooses IDs for its own requests independently, so the same ID can be in use in both directions. A sender **MUST NOT** reuse an ID while a request with that ID is still awaiting a response.

Expand Down
Loading