| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Instead of doing this when we construct the listeners, we can do it
in a separate method, to simplify the return type.
|
| | |
|
| |
|
|
|
|
| |
Previous documentation was more-or-less meant for the Arti developer
only. This new documentation is intended for actual users of RPC
functionality. It's meant to be extracted with `maint/rpc-doc-tool`.
|
| |
|
|
|
|
|
| |
Without this, we get a panic on startup when running with RPC!
(This stresses the need for an integration test for RPC;
I will start writing that after the Python wrapper lands.)
|
| |
|
|
|
|
|
| |
Renamed address to tcp_address, and made it optional, so that later
we can have a unix_path, etc.
On deser side, add support for unrecognized listener types.
|
| | |
|
| |
|
|
|
|
|
|
| |
Currently this behaves the same as get_proxy_info,
but this may change in the future, if we introduce RPC-unsuitable
proxy ports.
(Also rename the get_proxy_info method to avoid x_ prefix.)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
(This is a bit trickier than I would like, but it ensures that we
never return a "not initialized yet" code.)
|
|
|
We'll need this for our rpc-library code to meaningfully open SOCKS
connections.
Closes #1523.
|