mirrors/arti.git/crates/arti-rpc-client-core/src/ffi.rs, branch arti-v1.2.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.82024-09-19T00:30:00Zrpclib: Use prop351 protocol to open streams.2024-09-19T00:30:00ZNick Mathewsonnickm@torproject.org2024-09-18T23:35:42Zurn:sha1:56b60b5b84222c78bae75f28fb5d185eac71b319
Now that prop351 is what Arti speaks, it's what the rpclib
needs to provide.
Note one change in particular: the `isolation` string
is no longer an optional argument when opening a stream.
(With prop351, there is no longer such a thing as an "absent"
isolation string, and we don't want to imply that there is a
difference between None and "".)
rpclib: Rename "connect" to "open_stream" as appropriate.2024-09-10T19:41:33ZNick Mathewsonnickm@torproject.org2024-09-10T19:41:33Zurn:sha1:7ed0e1216439f3b7ad7a662f47b3a6f947627e13rpclib: FFI for opening data streams.2024-09-09T14:52:56ZNick Mathewsonnickm@torproject.org2024-08-26T15:31:18Zurn:sha1:8fd335e5ae7ad761efe3030e33b7004ec70fc2ff
There's a blocking TODO here about exposing socks error codes that
I still need to solve.
rpclib, ffi: Allow simultaneous calls to `arti_rpc_handle_wait()`2024-08-27T13:45:12ZNick Mathewsonnickm@torproject.org2024-08-22T15:21:48Zurn:sha1:76e6a24759b5fc1a04b53077acb19afb82c8df88
Its underlying function previously took `&mut RpcHandle`,
which was an accident waiting to happen. Now it takes `&RpcHandle`
and includes a Mutex to prevent multiple threads from waiting for
updates on the same request ID at once.
As an alternative, we *could* try to update connimpl::Receiver to
allow multiple simultaneous listeners on the same request ID.
But that would (I think) require a lot more bookkeeping, and thus
would be a bit more error-prone.
Closes #1532.
ffi: Add support for request handles2024-08-12T18:35:09ZNick Mathewsonnickm@torproject.org2024-08-06T15:57:54Zurn:sha1:2364c6dc6d2fd16f08641a1fed2cbc970005dc66
This API allows the caller to launch a request and then watch for
updates on it.
ffi: New out_val_opt type for outptrs to non-pointers2024-08-12T18:34:12ZNick Mathewsonnickm@torproject.org2024-08-06T15:11:47Zurn:sha1:8cd3d9520963d5b01fda67330f8960e7822faf4e
Previously, we had out_ptr_opt for functions that wanted to return a
newly allocated `ArtiRpcFoo` via a `struct ArtiRpcFoo **` argument.
But we didn't have a way to return non-allocated `int` via an `int
*` argument. This code provides that.
FFI: Expose the object ID for the session.2024-08-06T18:45:49ZNick Mathewsonnickm@torproject.org2024-08-06T18:02:14Zurn:sha1:d5a996f5319c2b7ffb3d0673aa266ede549da0c1
(Without this, it isn't actually possible to use the RPC subsystem.)
ffi: Add some explicit ()s to prove they are there.2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-31T17:25:29Zurn:sha1:c4f8b574cfe7c35db3cc074fec59937b051b9c93ffi: Document safety for each function using ffi_body_raw.2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-31T13:00:04Zurn:sha1:6961e83f6ecbd975d7ed3610d6170a76240cac1affi: rename ffi_body_simple to ffi_body_raw2024-07-31T17:54:16ZNick Mathewsonnickm@torproject.org2024-07-31T12:50:29Zurn:sha1:5cdfa510127ea53126b1398f44e26b2fd540326f