mirrors/arti.git/crates/arti-client/src/rpc.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-08-18T16:09:04Zproto: Move the `stream` module under `client` (breaking).2025-08-18T16:09:04ZGabriela Moldovangabi@torproject.org2025-08-18T15:52:38Zurn:sha1:702e7276898d3f31e22033c5b64fea91703f3701
The `stream` module is client-specific, for the most part, so I am
moving it under `client`. Later on, we will factor out the parts that
can be shared with the relay implementation.
Note: this is a breaking change as the deleted `stream` module was
`pub`. We could've kept the module and reexported from it the public
types from `tor_proto::client::stream`, but I think it's better to have
this `client` namespacing, because it makes the separation between the
client and relay parts clearer.
rpc: Correct API documentation about optimism2025-01-30T15:08:17ZNick Mathewsonnickm@torproject.org2025-01-30T15:03:04Zurn:sha1:fcb10040764db7204b637713b4166c4f57235257
Our documentation had dated to an older version of our RPC stream
code, where all streams were automatically optimistic.
But as explained, our use of "optimistic"ness in RPC stream code is
now purely internal, to make it possible to get an DataStreamCtrl.
This isn't user-visible in our rpc_conn_open_stream code.
Closes #1583
fix: fix typos2025-01-06T20:36:37ZDimitris Apostoloudimitris.apostolou@icloud.com2024-12-25T20:48:02Zurn:sha1:4acfc23b70c51d2637d0274943a82d1c94dec050RPC: Rename "arti:isolated_client" to "arti:new_isolated_client".2024-10-09T18:56:49ZNick Mathewsonnickm@torproject.org2024-10-09T18:56:49Zurn:sha1:f0ac66d5516afe7aee3ed216ace256591d47ea3b
Closes #1678.
Revise RPC documentation to be more informative.2024-10-02T13:41:24ZNick Mathewsonnickm@torproject.org2024-10-01T19:52:22Zurn:sha1:ce737947586f444ec104166394894386a9b48e43
Previous documentation was more-or-less meant for the Arti developer
only. This new documentation is intended for actual users of RPC
functionality. It's meant to be extracted with `maint/rpc-doc-tool`.
rpc: Rename SingletonId to SingleIdResponse2024-09-24T14:23:53ZNick Mathewsonnickm@torproject.org2024-09-24T14:21:17Zurn:sha1:bd9b29b05de6c133b93366acb69d9e2ce6b126cd
Calling it "singleton" might have suggested that it was using the
[singleton pattern](https://en.wikipedia.org/wiki/Singleton_pattern),
which it isn't.
(Renaming done with rust-analyzer and double-checked with `git grep`.)
Closes #1585.
Add a TODO RPC call about revising/moving documentation2024-09-09T15:19:29ZNick Mathewsonnickm@torproject.org2024-09-09T14:12:13Zurn:sha1:014baea6ac8aaf4d86efb101cdb2f0517f811953rpc: More specificity surrounding SOCKS-rpc integration2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-09-04T17:39:51Zurn:sha1:56bd675297f2302cf805677259139f90f6b6736arpc: Refactor errors part 1: a new RpcMethod trait.2024-07-25T12:43:30ZNick Mathewsonnickm@torproject.org2024-07-23T17:23:58Zurn:sha1:c7c630c44d9e937d7185f591d75fd42c33ab5238
It is no longer necessary to say, for every RPC method,
that its error type is RpcError.
Several typo fixes from Gabi2024-06-11T21:02:04ZNick Mathewsonnickm@torproject.org2024-06-11T20:59:44Zurn:sha1:5a2fb68b19d71b4bd477aa08005f08e05d5438ad