summaryrefslogtreecommitdiff
path: root/crates/arti-rpcserver/src/connection.rs
Commit message (Collapse)AuthorAgeFilesLines
* rpc: Expand and clarify and cross-reference lock hierarchyIan Jackson2023-06-161-0/+2
|
* rpc: Document relationship between `Connection` and `RpcSession`Ian Jackson2023-06-161-0/+6
|
* rpc: Give the session-creation function an argument.Nick Mathewson2023-06-151-1/+1
| | | | | | 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.Nick Mathewson2023-06-151-7/+21
| | | | | | | | | | | | | | 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<dyn Fn()...> 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: connection_id _is_ used: remove a comment to the contraryNick Mathewson2023-06-141-3/+0
|
* rpc: revise the relationship between Mgr and ConnectionNick Mathewson2023-06-141-6/+18
| | | | | | | | 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.
* rpc: make decl_object! responsible for writing impl Object {} blocks.Nick Mathewson2023-06-071-1/+0
|
* RPC: Give out and accept GlobalIds for appropriate objects.Nick Mathewson2023-06-051-9/+71
|
* RPC: Implement a "global identifier" for non-session-bound IDsNick Mathewson2023-06-051-6/+29
| | | | | | | These identifiers are actually only "global" with respect to a given `RpcMgr`, but they should not be forgeable or reusable across RpcMgr objects. We're going to use them so that we have a kind of identifier for `TorClient`s that we can expose to SOCKS.
* rpc: Slightly refactor GenIdx encoding.Nick Mathewson2023-06-051-1/+1
|
* rpc: Give RpcMgr a registry of connections.Nick Mathewson2023-06-051-0/+16
| | | | | We're going to use this to implement arti#863, which requires that some RPC objects be globally nameable.
* rpc: Remove downgrade_owned for nowNick Mathewson2023-05-241-12/+0
| | | | | | | 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 sessionNick Mathewson2023-05-241-0/+33
| | | | | | | | | | | 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: Make the top-level returned object a "session".Nick Mathewson2023-05-241-32/+2
| | | | | | This will make it easier to change the semantics of what exactly we return, whether it has to be/contain a client, whether you can use it to look up all the live objects, &etc.
* rpc: move existing auth code to new module.Nick Mathewson2023-05-231-72/+2
|
* rpc: rename GenIdx::into/try_from implementationsNick Mathewson2023-05-151-3/+3
| | | | | These are about to become nondeterministic-ish and probably shouldn't use the Into/TryFrom traits.
* RPC: Make the "client" return optional.Nick Mathewson2023-05-041-2/+2
|
* RPC: Rename session.rs to connection.rsNick Mathewson2023-05-041-0/+494
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 23:29:32 +0000