<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rpcbase/src/dispatch.rs, branch arti-v1.2.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-03T08:09:02Z</updated>
<entry>
<title>Fix typos</title>
<updated>2024-09-03T08:09:02Z</updated>
<author>
<name>Dimitris Apostolou</name>
<email>dimitris.apostolou@icloud.com</email>
</author>
<published>2024-09-03T08:09:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=676f913463b7d84f34dd6101b99d03ef79cf57ad'/>
<id>urn:sha1:676f913463b7d84f34dd6101b99d03ef79cf57ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpcbase: Implement RPC method delegation support.</title>
<updated>2024-08-14T15:52:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-14T15:52:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3d18a0b83556dada0279f2dd6681d81391e57177'/>
<id>urn:sha1:3d18a0b83556dada0279f2dd6681d81391e57177</id>
<content type='text'>
(Couldn't use Deref here, since we needed to get an Arc.)

Only one delegation target per object is permitted for now.

This will help with #1523.
</content>
</entry>
<entry>
<title>rpcbase: Feature to list the RPC methods and what they apply to.</title>
<updated>2024-08-13T00:27:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-12T16:02:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=89543b0010f550a5699293d7b3f07752971be6a4'/>
<id>urn:sha1:89543b0010f550a5699293d7b3f07752971be6a4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpcbase: Facility for looking up RPC method information</title>
<updated>2024-08-13T00:19:20Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-12T14:09:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5883a585d74e2e95a13fd804b3281f72dd57525b'/>
<id>urn:sha1:5883a585d74e2e95a13fd804b3281f72dd57525b</id>
<content type='text'>
We'll need this to refer to the names of RPC methods as visible to
the caller, and to cross-reference them  with their related types.
</content>
</entry>
<entry>
<title>rpcbase: Expose Invocable type names directly.</title>
<updated>2024-08-12T13:57:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-12T13:57:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f976408e0f208679154577e511723cecaacb6b00'/>
<id>urn:sha1:f976408e0f208679154577e511723cecaacb6b00</id>
<content type='text'>
Previously, we exposed them only via `describe_invocable`, which
would have required the caller to parse a string in order to find
these.
</content>
</entry>
<entry>
<title>rpc: Refactor errors part 1: a new RpcMethod trait.</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T17:23:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c7c630c44d9e937d7185f591d75fd42c33ab5238'/>
<id>urn:sha1:c7c630c44d9e937d7185f591d75fd42c33ab5238</id>
<content type='text'>
It is no longer necessary to say, for every RPC method,
that its error type is RpcError.
</content>
</entry>
<entry>
<title>rpcbase: remove now-unused invoke methods</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T15:12:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=110625889e9137647c445dc12d4877ae56cc037c'/>
<id>urn:sha1:110625889e9137647c445dc12d4877ae56cc037c</id>
<content type='text'>
These methods were defined on DispatchTable, and then replaced by
top-level functions in the crate.  (The reason for using top-level
functions instead is so that we get the locking on the dispatch
table correct.)
</content>
</entry>
<entry>
<title>rpcbase: Remove a TODO RPC about duplication</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T14:54:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2691f3b5a6a6fda52b418a26718593739d124331'/>
<id>urn:sha1:2691f3b5a6a6fda52b418a26718593739d124331</id>
<content type='text'>
The duplication is only a few lines. I've looked into a couple of
ways for removing it, but they make the code flow even less clear.
</content>
</entry>
<entry>
<title>rpc: Remove TODO about moving @special to a different macro.</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T14:01:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=03bd8e242d570a9d62c5dbe82e1e1b0bd46a035a'/>
<id>urn:sha1:03bd8e242d570a9d62c5dbe82e1e1b0bd46a035a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpcbase: tests for crate-level invoke functions.</title>
<updated>2024-07-16T00:17:38Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-16T00:17:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7692adb7ff4c99fb2c964d793326960bb6b8d5bb'/>
<id>urn:sha1:7692adb7ff4c99fb2c964d793326960bb6b8d5bb</id>
<content type='text'>
</content>
</entry>
</feed>
