mirrors/arti.git/crates/arti/src/rpc.rs, branch arti-v1.2.6

RPC: Use RPC methods instead of the "ClientConnectionTarget" trait.

2024-06-11T21:02:04Z

On its own, this might not seem like a huge improvement, but it will later let us implement these RPC methods for types that can't reasonably implement ClientConnectionTarget. It also serves as a proof of concept that special-method invocation can actually work, so that we can build things like this in cases where introducing a trait isn't practical. Closes #1427

RPC: Give error from RpcMgr::new if method name is sufficiently bad.

2024-05-14T13:49:44Z

(We don't give an error about unrecognized namespaces (for now), since we have no way to opt in to them.)

RPC: Enforce method name format.

2024-05-14T13:39:47Z

We need to do this carefully, since we want our system to be extensible with new namespaces. First, when we are constructing an RpcMgr, we _warn_ about any method names that are misformed. Second, we add a test in the `arti` crate to fail if any method names are invalid. This will only catch method names in crates that `arti` depends on.

RPC: RpcDataStream type to act as a "stream-shaped hole"

2024-05-14T12:04:03Z

The application creates these, using a new-stream-handle RPC command, on an object that can actually create streams. Then later, the application provides the (global) identity of one of these objects when it's making a SOCKS connection. This causes the object to take hold of a `DataStreamCtrl`.

TorClient: Slightly cleaner (?) interface for registering RPC methods.

2024-05-06T13:12:08Z

RPC: Implement methods to get and watch client bootstrap status.

2024-05-06T13:12:08Z

rpc: Give the session-creation function an argument.

2023-06-15T15:50:12Z

This will later let us tell the session-creation function how the authentication occurred, which will let it decide what privileges to provide.

rpc: revise session initialization a lot.

2023-06-15T15:44:14Z

Formerly, every time we wanted to launch a new connection, we had to give the RpcMgr a TorClient. The connection would hold that TorClient until a session was authenticated, and then would wrap it in a Session and put it in the object map. Now, the RpcMgr holds a Box that knows how to create Sessions. When a connection is authenticated, it asks the Mgr to make it a new session. This lets us make it clearer that the TorClient simply can't be given out until the connection is authenticated. Later, it will let us create more types of Session objects under more complicated rules.

RPC: rename new_session to new_connection

2023-06-15T15:15:40Z

rpc: revise the relationship between Mgr and Connection

2023-06-14T18:43:08Z

This adds a Weak reference from Connection to Mgr, makes DispatchTable mutable, and makes a few other changes as discussed between me and Diziet the other week. I bet we are not done tweaking this, but I hope it's a setp forwards.