summaryrefslogtreecommitdiff
path: root/doc/dev/notes/rpc-meta-draft.md
Commit message (Collapse)AuthorAgeFilesLines
* rpc-meta-draft.md: correct some minor typosJim Newsome2024-09-251-7/+7
|
* rpc-draft: move cancel method to connection object.Nick Mathewson2024-09-111-1/+1
|
* rpc: Add a "client implementation strategies" section.Nick Mathewson2024-09-111-1/+24
|
* rpc: Document pipelining and concurrency.Nick Mathewson2024-09-111-2/+15
|
* rpc: Add a "Cancelled" code to our docs.Nick Mathewson2024-09-111-0/+1
|
* rpc: Replace strong/weak objectIds with reference/handle againNick Mathewson2024-09-111-5/+18
| | | | | Diziet prefers this terminology; we'll defer a reckoning here till #849 is resolved.
* rpc-draft: Adopt a stricter-but-looser rule for anti-framing defenseNick Mathewson2024-09-111-13/+46
| | | | | | | Instead of saying "no errors before authentication", we now say "no syntax errors ever." This should be easier to implement.
* rpc-draft: A few more tweaks based on review.Nick Mathewson2024-09-111-10/+12
|
* Several rpc-draft suggestions from diziet.Nick Mathewson2024-09-111-11/+22
|
* rpc-meta: Note that the appendix is obsolete.Nick Mathewson2024-09-111-0/+3
|
* rpc-meta: Note that most listed requests are hypotheticalNick Mathewson2024-09-111-0/+4
|
* rpc-meta: remove example apis sectionNick Mathewson2024-09-111-58/+0
| | | | (This is obsoleted by arti-rpc-client-core.)
* rpc-meta: update cancellation to latest thinkingNick Mathewson2024-09-111-16/+6
|
* rpc-meta: Tweaks to "authentication" section.Nick Mathewson2024-09-111-5/+10
|
* rpc-meta: clarify current method name rules.Nick Mathewson2024-09-111-8/+9
| | | | | | | | Notably, identifiers SHOULD be C identifiers, and everything has a namespace. Reserve "rpc" as a namespace for things that were previously unnamespaced.
* rpc-meta: Light edits to parameter description.Nick Mathewson2024-09-111-3/+3
|
* rpc-meta: Rewrite and move documentation on object semantics.Nick Mathewson2024-09-111-32/+117
| | | | | This is probably still far too informal, but it is better than our previous documentation.
* rpc-meta: clarify status of Sessions.Nick Mathewson2024-09-111-0/+7
| | | | | (Note what isn't implemented, and one more kind of authentication we'll likely build someday.)
* rpc-meta: rewrite front matterNick Mathewson2024-09-111-29/+38
|
* rpc-meta: Add a top-level heading, and shift other headingsNick Mathewson2024-09-111-35/+37
| | | | (Markdown convention deprecates having more than one top-level heading.)
* rpc: Remove RpcError data field and use ReportNick Mathewson2024-07-251-26/+44
| | | | | | | | | | | | Per discussion, this field isn't really specified in a way that lets us fill it sensibly at the moment. So for now, we're going to just omit it. Additionally, we said that we'd Report on our errors; this branch changes the implementation of RpcError to do that. Question: Will the blanket implementation for Into<RpcError> make it harder to re-add a Data field later on if we want to do so?
* rpc: split "method not found"Nick Mathewson2024-07-251-1/+2
| | | | | We've wanted separate error codes for "no such method exists" and "this method exists, but this object doesn't have it."
* Tests and documentation about NULs in the RPC stream.Nick Mathewson2024-07-161-0/+4
|
* Fix typos in documentationTobias Stoeckmann2024-03-061-2/+2
|
* Fix typosDimitris Apostolou2023-07-221-1/+1
|
* rpc: update rpc-meta-draft with new behavior.Nick Mathewson2023-05-241-3/+7
|
* rpc: Clarify how authentication works.Nick Mathewson2023-05-161-10/+5
|
* rpc: Clarify some object ID docs and remove impl details.Nick Mathewson2023-05-161-37/+4
|
* rpc: Revise example in documentationNick Mathewson2023-05-161-4/+4
|
* rpc spec: define method namespacing.Nick Mathewson2023-04-131-5/+29
| | | | Closes #822
* rpc, spec: Document current ObjectError, RequestError behavior as correct.Nick Mathewson2023-04-131-2/+2
|
* rpc: Change `id=<SYNTAX>` to "no id".Nick Mathewson2023-04-131-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 Mathewson2023-04-121-0/+6
|
* rpc spec: Change arti_kinds => kinds per discussion.Nick Mathewson2023-04-121-6/+11
|
* rpc: terminology edits around "method" in spec draftNick Mathewson2023-04-121-4/+4
| | | | | | Always "method", never "command". Always "authentication scheme", never "authentication method".
* Add notes on how to test the RPC engineNick Mathewson2023-04-121-0/+1
|
* Add notes on how to test the RPC engineNick Mathewson2023-04-121-0/+27
|
* rpc: Fix typos/grammar errorsNick Mathewson2023-04-111-2/+2
|
* rpc: Rewrite `data` spec in JSON termsIan Jackson2023-04-111-4/+12
|
* rpc: Clarify that error formatting display is indicativeIan Jackson2023-04-111-0/+4
|
* Use non-JSON-RPC-reserved values for our own errorsIan Jackson2023-04-111-2/+4
|
* rpc: Fix mistake in "JSON-RPC compatibility" section for errorsIan Jackson2023-04-111-1/+2
|
* rpc: Discourage use of `code`Ian Jackson2023-04-111-1/+8
|
* rpc: Warn about relying too much about `data`Ian Jackson2023-04-111-0/+5
|
* rpc: Provide example of an error responseIan Jackson2023-04-111-0/+18
|
* rpc: Provide a list of ErrorKind stringsIan Jackson2023-04-111-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 Jackson2023-04-111-1/+1
|
* rpc: Be more explicit about what the string error message is forNick Mathewson2023-04-111-1/+3
|
* rpc: Proposed error formatIan Jackson2023-04-111-0/+52
|
* Merge branch 'rpc' into 'main'Ian Jackson2023-04-041-43/+122
|\ | | | | | | | | Proposed rpc protocol edits and tightenings-up See merge request tpo/core/arti!1078
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-27 07:28:26 +0000