-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New jsonrpc-core with futures and metadata support #3859
Conversation
Conflicts: Cargo.lock Cargo.toml parity/dapps.rs parity/rpc.rs parity/signer.rs
Conflicts: rpc/src/v1/impls/traces.rs rpc/src/v1/traits/traces.rs
Conflicts: Cargo.lock rpc/src/v1/impls/eth.rs signer/src/tests/mod.rs
Changes Unknown when pulling 4f494d5 on rpc-futures into ** on master**. |
looks reasonable to me. |
will need rebase... |
Conflicts: Cargo.lock Cargo.toml parity/rpc_apis.rs parity/run.rs rpc/Cargo.toml rpc/src/lib.rs rpc/src/v1/tests/mocked/parity_set.rs rpc/src/v1/traits/parity_set.rs
still some conflicts... |
Conflicts: Cargo.lock rpc/src/v1/impls/eth.rs
#[derive(Clone, Debug, PartialEq)] | ||
pub enum Origin { | ||
/// RPC server | ||
Rpc, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does an origin of Rpc
signify? All requests are RPC requests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's JSON-RPC over HTTP coming from standalone JSON-RPC server (not dapps). It's initialized in crate rpc
and also parity/rpc.rs
so I thought that it makes sense to use this name to indentify it.
IMHO it shouldn't go to |
Changes Unknown when pulling 06c9be9 on rpc-futures into ** on master**. |
Conflicts: Cargo.lock Cargo.toml dapps/src/lib.rs dapps/src/tests/helpers.rs parity/dapps.rs parity/rpc_apis.rs parity/run.rs rpc/Cargo.toml rpc/src/lib.rs rpc/src/v1/impls/parity_set.rs
Conflicts: Cargo.lock dapps/src/rpc.rs
Changes Unknown when pulling 969f5c0 on rpc-futures into ** on master**. |
requires rebase |
Conflicts: Cargo.lock dapps/src/lib.rs dapps/src/tests/helpers/mod.rs parity/dapps.rs parity/rpc.rs parity/run.rs rpc/src/lib.rs rpc/src/v1/impls/eth.rs rpc/src/v1/impls/traces.rs rpc/src/v1/tests/mocked/signer.rs stratum/src/lib.rs util/fetch/src/client.rs
jsonrpc-core
was rewritten to useFutures
to handle async code.Metadata
is now part ofjsonrpc-core
, so there is no need to do middlewares and augmentationThis will allow us to handle requests coming from different transports in a more elegant way (for instance
eth_accounts
can return all accounts for HTTP and IPC and only alter the list for dapps).