The sw&rpc client instance, which provides methods to call procedures.
Each property of the procedures map will be a method, that accepts an input, an optional onProgress callback and an optional request ID.
If you want to be able to cancel the request, you can set the request's ID yourself, and call .abort(requestId, reason) on the client instance to cancel it.
The sw&rpc server instance, which provides methods to register procedure implementations, and listens for incoming messages that call those procedures
A procedure declaration
A promise that you can cancel by calling .cancel(reason) on it:
An implementation of a procedure
Declarations of procedures by name.
Declaration of hooks to run on messages received from the server
The callable function signature for a client method
A procedure that broadcasts its request to multiple nodes. The return value is an array of results, along with extra properties: see BroadcasterResultExtrasMixed, BroadcasterResultExtrasSuccess and BroadcasterResultExtrasFailure
Extra properties on the result of a broadcaster call, when some nodes succeeded and some failed
Extra properties on the result of a broadcaster call, when all nodes succeeded
Extra properties on the result of a broadcaster call, when all nodes failed
A procedure's corresponding method on the client instance -- used to call the procedure. If you want to be able to cancel the request, you can use the cancelable method instead of running the procedure directly.
Names that can't be used as procedure names. Will fail at runtime, when starting the client.
A cancelable request was cancelled (either via .cancelable's .cancel() or via a .once / .onceBy call)