mirrors/arti.git/crates/tor-rpcbase/src, branch arti-v1.1.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.52023-05-24T14:15:56Zrpc: Remove downgrade_owned for now2023-05-24T14:15:56ZNick Mathewsonnickm@torproject.org2023-05-24T13:24:45Zurn:sha1:936387efee359a38a22a920568090b204dfd07be
Rationale: Our weak-vs-strong design is a bit confused at the moment
due to concerns about deduplication and capability semantics. It's
not clear that a general "change strong to weak" method is
compatible with what we want to provide.
rpc: Implement functionality to remove objects from a session2023-05-24T14:15:56ZNick Mathewsonnickm@torproject.org2023-05-23T14:41:56Zurn:sha1:9713e8d3054aafe3f19afd55693bc3159712e595
I've made doing some design choices here:
* Reserving "rpc" as a prefix for post-authentication
functionality that is not arti-specific.
* Declaring these to be methods on the session rather than methods
on the objects themselves.
There's a problem with defining an API to drop a weak reference; see
comment in code.
rpc: fix documentation for methods in Context.2023-05-24T14:15:56ZNick Mathewsonnickm@torproject.org2023-05-23T14:17:25Zurn:sha1:15a8644bf7dd3b8d98a485b808af3dfba7f7f6a6RPC: Add "register" methods to RequestContext.2023-05-04T14:35:05ZNick Mathewsonnickm@torproject.org2023-04-25T21:08:47Zurn:sha1:9be9ddb9027fef615613118451bc7e98fbc533b5RPC: Log all internal errors.2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-19T16:35:49Zurn:sha1:7c1f45a514c0c6f5579be939151a3f75db62d731rpc: Simplify and clarify SendUpdateError.2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-19T16:30:38Zurn:sha1:ffcbd8fe8840f9b2e946b52714d79be04f61f073Arti: Add ability to remember the list of methods names.2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-18T22:43:16Zurn:sha1:accd3d858f9812eba326306014a9543590d93dad
Right now, this lets us say whether the method was unrecognized or
whether the parameter type was incorrect.
We'll use this to enforce correct method names later on.
(I have to add another `inventory` here, since the `typetag`
maintainer does not want to expose this functionality: see
https://github.com/dtolnay/typetag/issues/57#issuecomment-1506106290
)
rpc: New syntax for method declaration2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-18T21:37:27Zurn:sha1:e6092e99ea356664be8286d17b8e2526576fa6ee
Now you just declare your function `my_func` with the right types,
and invoke `rpc_invoke_fn!{ my_func(ObjType, MethodType); }`
rpc: impl From<SendUpdateError> for RpcError.2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-18T20:26:31Zurn:sha1:a415b0e2d21d3a35c86ed4f8478486de1750166drpcbase: Use with_fn.2023-04-19T16:38:26ZNick Mathewsonnickm@torproject.org2023-04-18T19:52:14Zurn:sha1:6f6a4d073e1f92758264f99e290968e7853ba0cd