<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rpcbase/src, branch arti-v1.2.8</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.8</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-25T15:25:52Z</updated>
<entry>
<title>Merge branch 'rename_singleton_id' into 'main'</title>
<updated>2024-09-25T15:25:52Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-09-25T15:25:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8753eb8294ff4eedf4f4d6ba26e918a7eb1635aa'/>
<id>urn:sha1:8753eb8294ff4eedf4f4d6ba26e918a7eb1635aa</id>
<content type='text'>
rpc: Rename SingletonId to SingleIdResponse

Closes #1585

See merge request tpo/core/arti!2448</content>
</entry>
<entry>
<title>rpc: Expose a delegation table in arti:x_list_all_rpc_methods</title>
<updated>2024-09-24T14:45:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-16T14:54:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=438407b6b335b984ce84b4f65ac0b3cd7ec99aa2'/>
<id>urn:sha1:438407b6b335b984ce84b4f65ac0b3cd7ec99aa2</id>
<content type='text'>
Closes #1624.
</content>
</entry>
<entry>
<title>rpc: add mandatory delegate-type attribute to Object template</title>
<updated>2024-09-24T14:45:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-16T14:29:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0c7fc748144c8a6b80ce422e6c0055dc1497285e'/>
<id>urn:sha1:0c7fc748144c8a6b80ce422e6c0055dc1497285e</id>
<content type='text'>
When specifying a delegation, the template user must also say what
type they're delegating to.

We're going to use this to document and expose delegations.
</content>
</entry>
<entry>
<title>rpc: Rename SingletonId to SingleIdResponse</title>
<updated>2024-09-24T14:23:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-24T14:21:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bd9b29b05de6c133b93366acb69d9e2ce6b126cd'/>
<id>urn:sha1:bd9b29b05de6c133b93366acb69d9e2ce6b126cd</id>
<content type='text'>
Calling it "singleton" might have suggested that it was using the
[singleton pattern](https://en.wikipedia.org/wiki/Singleton_pattern),
which it isn't.

(Renaming done with rust-analyzer and double-checked with `git grep`.)

Closes #1585.
</content>
</entry>
<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>Add a missing incantation to fix doc(cfg=...).</title>
<updated>2024-08-13T12:25:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-13T12:25:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3d0c1bb3809af575d0c519efb43f5e2d197047c5'/>
<id>urn:sha1:3d0c1bb3809af575d0c519efb43f5e2d197047c5</id>
<content type='text'>
Without this, we get a warning when we run `cargo doc`.
</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>
</feed>
