mirrors/arti.git/crates/arti-rpc-client-core/src/ffi.rs, branch arti-v1.4.1

Merge branch 'rpc_document_internal_optimism' into 'main'

2025-01-30T18:28:11Z

rpc: Document what is actually going on with stream optimism. Closes #1583 See merge request tpo/core/arti!2753

rpc: Correct API documentation about optimism

2025-01-30T15:08:17Z

Our documentation had dated to an older version of our RPC stream code, where all streams were automatically optimistic. But as explained, our use of "optimistic"ness in RPC stream code is now purely internal, to make it possible to get an DataStreamCtrl. This isn't user-visible in our rpc_conn_open_stream code. Closes #1583

fix: fix typos

2025-01-30T08:39:30Z

arti-rpc-client-core: Document that dropping a request does not cancel it.

2025-01-23T00:39:58Z

I hope that this limitation is acceptable; the alternative involves some significant refactoring to give Request a Weak reference to RpcConn -- but RpcConn isn't currently kept in an Arc<> at all, and so we'd need some fairly heavy hacking.

arti-rpc-client-core: Implement and expose cancellation.

2025-01-23T00:39:58Z

artilib: Revise C and Python APIs for builders.

2024-12-09T20:23:43Z

Expose ArtiRpcConnBuilder and appropriate C wrapper functions in our FFI code, and wrap those functions in our python wrapper. This breaks the old C API, but that's allowed since the API is still experimental. Some design decisions: * I've wrapped the builder in a Mutex, so that we can continue our FFI rule that we do not require non-Rust code to wrap `&mut`. * I've removed the non-builder connect() function from the C API as extraneous. * I've made a single function to prepend elements to the search path.

rpc-client: Initial implementation for RPC connect points.

2024-12-09T20:23:43Z

This commit covers the major points of the design: Parsing the environment, parsing and resolving connect points, connecting to Arti, and handling errors. There are a few areas that need to be fixed, all marked with XXXXs.

rpclib: Use prop351 protocol to open streams.

2024-09-19T00:30:00Z

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:33Z

rpclib: FFI for opening data streams.

2024-09-09T14:52:56Z

There's a blocking TODO here about exposing socks error codes that I still need to solve.