| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fix typos | Dimitris Apostolou | 2023-07-22 | 1 | -1/+1 |
| | | |||||
| * | rpc: update rpc-meta-draft with new behavior. | Nick Mathewson | 2023-05-24 | 1 | -3/+7 |
| | | |||||
| * | rpc: Clarify how authentication works. | Nick Mathewson | 2023-05-16 | 1 | -10/+5 |
| | | |||||
| * | rpc: Clarify some object ID docs and remove impl details. | Nick Mathewson | 2023-05-16 | 1 | -37/+4 |
| | | |||||
| * | rpc: Revise example in documentation | Nick Mathewson | 2023-05-16 | 1 | -4/+4 |
| | | |||||
| * | rpc spec: define method namespacing. | Nick Mathewson | 2023-04-13 | 1 | -5/+29 |
| | | | | | Closes #822 | ||||
| * | rpc, spec: Document current ObjectError, RequestError behavior as correct. | Nick Mathewson | 2023-04-13 | 1 | -2/+2 |
| | | |||||
| * | rpc: Change `id=<SYNTAX>` to "no id". | Nick Mathewson | 2023-04-13 | 1 | -3/+5 |
| | | | | | | | | Now instead of hoping that buggy clients will detect a magic `id`, we can simply tell them that they will get no `id` at all. If they can't handle that case, no major harm is done: the connection will get closed anyway. | ||||
| * | rpc spec: Allocate a special ID for syntax errors. | Nick Mathewson | 2023-04-12 | 1 | -0/+6 |
| | | |||||
| * | rpc spec: Change arti_kinds => kinds per discussion. | Nick Mathewson | 2023-04-12 | 1 | -6/+11 |
| | | |||||
| * | rpc: terminology edits around "method" in spec draft | Nick Mathewson | 2023-04-12 | 1 | -4/+4 |
| | | | | | | | Always "method", never "command". Always "authentication scheme", never "authentication method". | ||||
| * | Add notes on how to test the RPC engine | Nick Mathewson | 2023-04-12 | 1 | -0/+1 |
| | | |||||
| * | Add notes on how to test the RPC engine | Nick Mathewson | 2023-04-12 | 1 | -0/+27 |
| | | |||||
| * | rpc: Fix typos/grammar errors | Nick Mathewson | 2023-04-11 | 1 | -2/+2 |
| | | |||||
| * | rpc: Rewrite `data` spec in JSON terms | Ian Jackson | 2023-04-11 | 1 | -4/+12 |
| | | |||||
| * | rpc: Clarify that error formatting display is indicative | Ian Jackson | 2023-04-11 | 1 | -0/+4 |
| | | |||||
| * | Use non-JSON-RPC-reserved values for our own errors | Ian Jackson | 2023-04-11 | 1 | -2/+4 |
| | | |||||
| * | rpc: Fix mistake in "JSON-RPC compatibility" section for errors | Ian Jackson | 2023-04-11 | 1 | -1/+2 |
| | | |||||
| * | rpc: Discourage use of `code` | Ian Jackson | 2023-04-11 | 1 | -1/+8 |
| | | |||||
| * | rpc: Warn about relying too much about `data` | Ian Jackson | 2023-04-11 | 1 | -0/+5 |
| | | |||||
| * | rpc: Provide example of an error response | Ian Jackson | 2023-04-11 | 1 | -0/+18 |
| | | |||||
| * | rpc: Provide a list of ErrorKind strings | Ian Jackson | 2023-04-11 | 1 | -2/+17 |
| | | | | | | Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1107#note_2893078 | ||||
| * | rpc: Be more explicit about what the string error message is for (typo) | Ian Jackson | 2023-04-11 | 1 | -1/+1 |
| | | |||||
| * | rpc: Be more explicit about what the string error message is for | Nick Mathewson | 2023-04-11 | 1 | -1/+3 |
| | | |||||
| * | rpc: Proposed error format | Ian Jackson | 2023-04-11 | 1 | -0/+52 |
| | | |||||
| * | Merge branch 'rpc' into 'main' | Ian Jackson | 2023-04-04 | 1 | -43/+122 |
| |\ | | | | | | | | | Proposed rpc protocol edits and tightenings-up See merge request tpo/core/arti!1078 | ||||
| | * | rpc: Fix typos | Nick Mathewson | 2023-04-04 | 1 | -2/+2 |
| | | | |||||
| | * | rpc: Speak of "Arti" rather than "arti" | Ian Jackson | 2023-04-03 | 1 | -2/+2 |
| | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889618 | ||||
| | * | rpc: State the integer round-trip range limits | Ian Jackson | 2023-04-03 | 1 | -1/+5 |
| | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889617 | ||||
| | * | rpc: Don't talk about "properties" of objects: rather, "members" | Ian Jackson | 2023-04-03 | 1 | -1/+1 |
| | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889616 | ||||
| | * | rpc: Move notes about cancellation to right section | Ian Jackson | 2023-04-03 | 1 | -7/+7 |
| | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889614 | ||||
| | * | rpc: Be clearer about updates content | Ian Jackson | 2023-04-03 | 1 | -2/+3 |
| | | | | | | | | | | | | | | | | | You can't parse an update without knowing the request method (this was already stated elsewhere). Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889613 | ||||
| | * | rpc: Change how we talk about objects | Ian Jackson | 2023-04-03 | 1 | -1/+6 |
| | | | | | | | | | | | | | | | | | | | Use just "object" in the introduction, but be specific that the abstract data type is I-JSON, even if we later invent other representations. Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889612 | ||||
| | * | rpc: Right at top, say I-JSON | Ian Jackson | 2023-04-03 | 1 | -1/+1 |
| | | | | | | | | | | | Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889612 | ||||
| | * | rpc: Change wording about responses | Ian Jackson | 2023-04-03 | 1 | -1/+1 |
| | | | | | | | | | | | Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1078#note_2889611 | ||||
| | * | rpc: Start on a list of the differences with JSON-RPC | Ian Jackson | 2023-03-24 | 1 | -0/+23 |
| | | | |||||
| | * | rpc: Discuss ordering and buffering | Ian Jackson | 2023-03-24 | 1 | -0/+13 |
| | | | |||||
| | * | rpc: Define term `field` | Ian Jackson | 2023-03-24 | 1 | -0/+2 |
| | | | |||||
| | * | rpc: Discuss cancellation request obj | Ian Jackson | 2023-03-24 | 1 | -0/+9 |
| | | | |||||
| | * | rpc: Clarify what precisely the responses depend on | Ian Jackson | 2023-03-24 | 1 | -2/+4 |
| | | | | | | | | | | | | | | | | | The format of an update or result depends on the *method* but not the parameters or the subject. Declare that the format of an error is uniform. (It could have an enum in it.) | ||||
| | * | rpc: State that we're using I-JSON | Ian Jackson | 2023-03-24 | 1 | -0/+8 |
| | | | |||||
| | * | rpc: Forbid troublesome numbers as ids | Ian Jackson | 2023-03-24 | 1 | -2/+4 |
| | | | | | | | | | | | This is a bit sad but I think we should have a conservative JSON profile. | ||||
| | * | rpc: Be more explicit about ignoring JSON fields | Ian Jackson | 2023-03-24 | 1 | -1/+4 |
| | | | |||||
| | * | rpc: Clarify/restate method definition requirements | Ian Jackson | 2023-03-24 | 1 | -9/+10 |
| | | | | | | | | | | | | | | | In particular, abolish the notion of a "response type". Since responses don't come with a discriminant, each method may have only one success response format (although of course that format might itself have optional fields or be an enum or something). | ||||
| | * | rpc: Use Object for method targets and JSON object for document objects | Ian Jackson | 2023-03-24 | 1 | -29/+31 |
| | | | |||||
| | * | rpc: Make `params` in a request non-optional | Ian Jackson | 2023-03-24 | 1 | -1/+5 |
| | | | | | | | | | | | | | *If* it is optional that would depend on the request, which is a bit complicated to specify precisely. And making it mandatory is more orthogonal. | ||||
| * | | Fix typo | Dimitris Apostolou | 2023-03-24 | 1 | -1/+1 |
| |/ | |||||
| * | rpc-meta-draft: Sketch an even-lower-level API. | Nick Mathewson | 2023-03-24 | 1 | -0/+11 |
| | | |||||
| * | rpc-draft: Sketch out more commands to add, start sketching APIs | Nick Mathewson | 2023-03-24 | 1 | -1/+112 |
| | | |||||
| * | rpc-meta: clarify when "object" means "JSON object". | Nick Mathewson | 2023-03-24 | 1 | -8/+7 |
| | | |||||
