diff --git a/papi-dts/classes/_client_services_rpc_client_.default.html b/papi-dts/classes/_client_services_rpc_client_.default.html index bb095f5653..de17e12ffe 100644 --- a/papi-dts/classes/_client_services_rpc_client_.default.html +++ b/papi-dts/classes/_client_services_rpc_client_.default.html @@ -1,6 +1,6 @@
Whether this connector is setting up or has finished setting up its connection and is ready to communicate on the network
-Sets up the RPC handler by populating connector info, setting up event handlers, and doing one of the following:
Function that handles events from the server by accepting an eventType and an event and emitting the event locally. Used when receiving an event over the network.
Promise that resolves when finished connecting
-Disconnects from the connection:
+Sends an event to other processes. Does NOT run the local event subscriptions as they should be +
Sends an event to other processes. Does NOT run the local event subscriptions as they should be run by NetworkEventEmitter after sending on network.
Unique network event type for coordinating between processes
Event data to emit on the network
-Register a method that will be called if an RPC request is made
-Register a method that will be called if an RPC request is made
+Send a request and resolve after receiving a response
Type of request (or "method" in JSONRPC jargon) to call
Parameters associated with this request
Promise that resolves to a JSONRPCSuccessResponse or JSONRPCErrorResponse message
-
Manages the JSON-RPC protocol on the client end of a websocket that connects to main
Created by any process that connects to the websocket server owned by main
-