A special base class for the set of all possible recipients, without having to identify who they all are.
RPC operations that the node exposes to clients.
A base class for a set of recipients specifically identified by the sender.
The interface for a group of message recipients (which may contain only one recipient)
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.
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.
A base class for the case of point-to-point messages
As an RPC Client, use this class to point to the truststore that contains the RPC SSL certificate provided by the node admin
The Data feed contains a snapshot of the requested data and an Observable of future updates.
Represents information about a flow (the name "state machine" is legacy, Kotlin users can use the FlowInfo type alias). You can access progress tracking, information about why the flow was started and so on.
Data types used by the Corda messaging layer to manage state of messaging and sessions between nodes.