Overview changedspecification/2024-11-05/basic/index
Nearest release: v2.1.284, published 4 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
4
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 4, old and new numbered
/
from line 4
44[JSON-RPC 2.0](https://www.jsonrpc.org/specification) specification. The protocol defines
55three fundamental types of messages:
66
7| Type | Description | Requirements |
8| --------------- | -------------------------------------- | -------------------------------------- |
9| `Requests` | Messages sent to initiate an operation | Must include unique ID and method name |
10| `Responses` | Messages sent in reply to requests | Must include same ID as request |
11| `Notifications` | One-way messages with no reply | Must not include an ID |
7| Type | Description | Requirements |
8| - | - | - |
9| `Requests` | Messages sent to initiate an operation | Must include unique ID and method name |
10| `Responses` | Messages sent in reply to requests | Must include same ID as request |
11| `Notifications` | One-way messages with no reply | Must not include an ID |
1212
1313**Responses** are further sub-categorized as either **successful results** or **errors**.
1414Results can follow any JSON object structure, while errors must include an error code and
No line in this hunk matches that.