mirrors/arti.git/crates/tor-rpcbase/src/dispatch.rs, branch arti-v1.1.5 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.5 2023-05-24T14:15:56Z rpc: Remove downgrade_owned for now 2023-05-24T14:15:56Z Nick Mathewson nickm@torproject.org 2023-05-24T13:24:45Z urn: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 session 2023-05-24T14:15:56Z Nick Mathewson nickm@torproject.org 2023-05-23T14:41:56Z urn: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: Add "register" methods to RequestContext. 2023-05-04T14:35:05Z Nick Mathewson nickm@torproject.org 2023-04-25T21:08:47Z urn:sha1:9be9ddb9027fef615613118451bc7e98fbc533b5 rpc: New syntax for method declaration 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T21:37:27Z urn:sha1:e6092e99ea356664be8286d17b8e2526576fa6ee Now you just declare your function `my_func` with the right types, and invoke `rpc_invoke_fn!{ my_func(ObjType, MethodType); }` rpcbase: Use with_fn. 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T19:52:14Z urn:sha1:6f6a4d073e1f92758264f99e290968e7853ba0cd rpc: Minor tweaks to get a sink to compile. 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T18:06:29Z urn:sha1:80a13ff898b5abd9002e56bdc388968f0006aa81 rpc: Use Method types to determine type of method outputs, updates. 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T17:53:01Z urn:sha1:0503f7bd4bd420df0b06cf9ccdd0b800646108bd This lets us do much less in our rpc_invoke_fn functions. rpc: Split Method into DynMethod and Method 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T17:04:28Z urn:sha1:7dcfb02c2201c29cb3237f5921a4130e6fcd567a Now `Method` has an Output and Update associated type, and `decl_method` can do a little more. rpc: simplify API by always providing a sink. 2023-04-16T12:46:42Z Nick Mathewson nickm@torproject.org 2023-04-14T16:35:01Z urn:sha1:5a2c38a1347d0508c59b81ec34732c1ed8fefddd Previously we have two places where we had to do "make a `Drain` sink if updates aren't wanted"; now there's only one. rpc: Wire updates into rpc invoke functions again. 2023-04-16T12:46:42Z Nick Mathewson nickm@torproject.org 2023-04-14T13:15:47Z urn:sha1:58ad91cbf56c95735e17286714960749750647dd Now that the sink is not part of the context, RPC functions that are able to send an update have to declare an `impl Sink` as their fourth argument. This syntax is not final. Part of #824.