See: Description
| Interface | Description |
|---|---|
| AllPossibleRecipients |
A special base class for the set of all possible recipients, without having to identify who they all are.
|
| CordaRPCOps |
RPC operations that the node exposes to clients.
|
| FlowHandle<A> |
interface FlowHandle is a serialisable handle for the started flow, parameterised by the type of the flow's return value. |
| FlowProgressHandle<A> |
interface FlowProgressHandle is a serialisable handle for the started flow, parameterised by the type of the flow's return value. |
| MessageRecipientGroup |
A base class for a set of recipients specifically identified by the sender.
|
| MessageRecipients |
The interface for a group of message recipients (which may contain only one recipient)
|
| RPCOps |
Base interface that all RPC servers must implement. Note: in Corda there's only one RPC interface. This base
interface is here in case we split the RPC system out into a separate library one day.
|
| RPCReturnsObservables |
If an RPC is tagged with this annotation it may return one or more observables anywhere in its response graph.
Calling such a method comes with consequences: it's slower, and consumes server side resources as observations
will buffer up on the server until they're consumed by the client.
|
| SingleMessageRecipient |
A base class for the case of point-to-point messages
|
| Class | Description |
|---|---|
| CordaRPCOpsKt | |
| DataFeed<A,B> |
The Data feed contains a snapshot of the requested data and an Observable of future updates.
|
| FlowHandleImpl<A> | |
| FlowProgressHandleImpl<A> | |
| StateMachineInfo | |
| StateMachineTransactionMapping | |
| StateMachineUpdate |
Data types used by the Corda messaging layer to manage state of messaging and sessions between nodes.