<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-rpcserver/src, branch arti-v1.3.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-10-25T18:52:35Z</updated>
<entry>
<title>Remove echo structs</title>
<updated>2024-10-25T18:52:35Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2024-10-25T18:52:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=133c0ac0c0d87d062bc2febe9bc355e25af11c2b'/>
<id>urn:sha1:133c0ac0c0d87d062bc2febe9bc355e25af11c2b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>arti-rpcserver: Remove echo_on_session</title>
<updated>2024-10-25T18:51:44Z</updated>
<author>
<name>Neel Chauhan</name>
<email>neel@neelc.org</email>
</author>
<published>2024-10-16T23:07:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=12301c4bfa97367af917a5889af08bfef5b7e125'/>
<id>urn:sha1:12301c4bfa97367af917a5889af08bfef5b7e125</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Tweak release_owned to give an error on second removal of "connection".</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-24T00:48:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=270234f81c3a2fc5f56fbe3d71cabad672237a78'/>
<id>urn:sha1:270234f81c3a2fc5f56fbe3d71cabad672237a78</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Use a const for the "connection" object ID.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-24T00:44:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=797a9d21dd856e62a0525130d34d5a992b7f9a7c'/>
<id>urn:sha1:797a9d21dd856e62a0525130d34d5a992b7f9a7c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Simplify method-dispatch-bypass logic a bit</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-24T00:33:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=eb1d9acd10c5d500f56d637a7bba3acdd67dc9e8'/>
<id>urn:sha1:eb1d9acd10c5d500f56d637a7bba3acdd67dc9e8</id>
<content type='text'>
This commit removes the separate function for asking whether to
bypass the dispatch code.  Instead, it gives the "invoke with
bypass" function an error to return when no dispatch is warranted,
and moves the whole responsibility for method dispatch or
non-dispatch back into tor-rpcbase.

I had to add an ObjectId argument to `invoke_rpc_method` to make
this work, but that's probably a good thing.

Additionally, this commit tweaks the derive-deftly macro to prevent
you from asking for dispatch bypass on special methods, where it
isn't implemented (and doesn't really make sense).
</content>
</entry>
<entry>
<title>rpc: Add support for dropping the special "connection" object ID.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T15:04:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=babc2f95d000499df4b8845fe2703d1270204505'/>
<id>urn:sha1:babc2f95d000499df4b8845fe2703d1270204505</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Move "rpc:release" to be a method on the rpc object.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T14:23:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fe1c2672d45391480a402b7cf3d2f75f4c23a2ac'/>
<id>urn:sha1:fe1c2672d45391480a402b7cf3d2f75f4c23a2ac</id>
<content type='text'>
Now, instead of telling the session or the connection to drop the
object ID, we tell the object ID to go away.

Closes #1663.
</content>
</entry>
<entry>
<title>rpcserver: detect and use methods that bypass method dispatch.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T13:56:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ec018b52e930c6c90e8fdd5d0a2a4853655fb7a1'/>
<id>urn:sha1:ec018b52e930c6c90e8fdd5d0a2a4853655fb7a1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rpc: Remove unimplemented rpc:downgrade method for now.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T12:10:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b748bbe2189158cb6ad2009ae60da6e03a44c084'/>
<id>urn:sha1:b748bbe2189158cb6ad2009ae60da6e03a44c084</id>
<content type='text'>
If and when we implement this, it will likely be different;
arti#868 has some thoughts on the implications.
</content>
</entry>
<entry>
<title>rpc: Move some object-id-manipulation methods to a new module.</title>
<updated>2024-10-24T01:35:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T12:09:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=318aaa2cfc571d99bcd711484e233420b0985c48'/>
<id>urn:sha1:318aaa2cfc571d99bcd711484e233420b0985c48</id>
<content type='text'>
These will have different implementations soon; this is a more
logical place for them.
</content>
</entry>
</feed>
