<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-rpcserver/src, branch arti-v1.2.6</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.6</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-07-28T21:48:35Z</updated>
<entry>
<title>Mark a struct as allowed-to-be-unused.</title>
<updated>2024-07-28T21:48:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-28T21:47:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b3dd3960fb25925718391852d94b275a204b269e'/>
<id>urn:sha1:b3dd3960fb25925718391852d94b275a204b269e</id>
<content type='text'>
(This will either become used later, or we will remove it;
the TODO RPC will remind us.)
</content>
</entry>
<entry>
<title>rpc: Rename the error codes for something like consistency.</title>
<updated>2024-07-25T12:46:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-24T18:51:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=847e80f307789c607ac3415254b292e20da9c7f0'/>
<id>urn:sha1:847e80f307789c607ac3415254b292e20da9c7f0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Remove RpcError data field and use Report</title>
<updated>2024-07-25T12:46:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T17:26:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2e9cc83fd918a40f551bcc3f9595956067044aad'/>
<id>urn:sha1:2e9cc83fd918a40f551bcc3f9595956067044aad</id>
<content type='text'>
Per discussion, this field isn't really specified in a way that lets
us fill it sensibly at the moment.  So for now, we're going to just
omit it.

Additionally, we said that we'd Report on our errors; this branch
changes the implementation of RpcError to do that.

Question: Will the blanket implementation for Into&lt;RpcError&gt; make
it harder to re-add a Data field later on if we want to do so?
</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>Several typo fixes from Gabi</title>
<updated>2024-06-11T21:02:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-11T20:59:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5a2fb68b19d71b4bd477aa08005f08e05d5438ad'/>
<id>urn:sha1:5a2fb68b19d71b4bd477aa08005f08e05d5438ad</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Un-indent a block.</title>
<updated>2024-06-11T21:02:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-05T16:05:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5654215e51eb514d6b72278706b7a859fc1c54e9'/>
<id>urn:sha1:5654215e51eb514d6b72278706b7a859fc1c54e9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>RPC: Use RPC methods instead of the "ClientConnectionTarget" trait.</title>
<updated>2024-06-11T21:02:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-04T17:22:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c07455965fd201ec66631e649a10660e5955e47c'/>
<id>urn:sha1:c07455965fd201ec66631e649a10660e5955e47c</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>rpc: Make RpcMgr::lookup_object return context along with object.</title>
<updated>2024-06-10T14:33:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-05T14:23:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9267b26bfcf35c5f8594953a75315165849a6828'/>
<id>urn:sha1:9267b26bfcf35c5f8594953a75315165849a6828</id>
<content type='text'>
The context will make it possible to invoke rpc methods.
</content>
</entry>
<entry>
<title>Implement rpc::Context on Connection directly</title>
<updated>2024-06-10T14:33:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-05T14:00:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aaf12c8970e35ff0f9873cf4c2e27adb2ccaf9e5'/>
<id>urn:sha1:aaf12c8970e35ff0f9873cf4c2e27adb2ccaf9e5</id>
<content type='text'>
This lets us get rid of a now-spurious `RequestContext` wrapper type
and an extra layer of indirection; it will also make it easier to
treat a Connection _as_ a context, so that we can have a context in
the socks-rpc interface code.

This patch removes a TODO about "treading carefully" when we make
this change.  When I added that TODO, I had misremembered some
implementation details of the RPC object system.
</content>
</entry>
<entry>
<title>rpc: allow Connection::lookup_object to take &amp;self</title>
<updated>2024-06-10T14:33:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-05T13:57:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3f7b69dd772c33175f41675e03b304da5c6ec508'/>
<id>urn:sha1:3f7b69dd772c33175f41675e03b304da5c6ec508</id>
<content type='text'>
This will allow us to implement rpc::Context on Connection directly.
</content>
</entry>
</feed>
