You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ockam_command crate contains some support to make RPC calls to a node. However this RPC support is also used to make local calls to a NodeManager.
The purpose of this story is to remove the Embedded mode from the Rpc struct so that local calls are made directly.
At the minimum this supposes to:
remove the integrating printing of response from the Rpc client
simplify the Rpc API and directly return typed values when possible (at the moment, the Rpc API exposes too many details about the processing of a response)
possibly revisit the necessity of a RpcBuilder (Maybe merge it within the Rpc struct)
simplify the creation of a Rpc into 2 distinct cases: "embedded" and "background"
make specific RPC clients for accessing: the controller, the project node, the authority node
create typed interfaces for each of those clients depending on their capabilities (for example the Controller can manage projects)
The
ockam_command
crate contains some support to make RPC calls to a node. However this RPC support is also used to make local calls to aNodeManager
.The purpose of this story is to remove the
Embedded
mode from theRpc
struct so that local calls are made directly.At the minimum this supposes to:
Rpc
clientRpc
API and directly return typed values when possible (at the moment, theRpc
API exposes too many details about the processing of a response)RpcBuilder
(Maybe merge it within theRpc
struct)Rpc
into 2 distinct cases: "embedded" and "background"Controller
can manage projects)RpcClient
NodeManagerWorker
andNodeManager
(all the logic should be in theNodeManager
)Connection
support for creating secure channelsThe text was updated successfully, but these errors were encountered: