Provides authentication information for HTTP RPC calls.
Represents an HTTP authentication scheme like Basic or Bearer
Interface to provide a Bearer token to HTTP RPC API calls
Implementation of FiniteDurableCursorBuilder which is created on the server side to be marshalled back to the client.
Methods of FiniteDurableCursorBuilder are not meant to be used, it is just a data container that wraps Cursor.PollResult.
HttpRpcClient is meant to run outside of Corda Node JVM and provide connectivity to a node using the HTTP-RPC protocol.
Since Corda Node can expose multiple RPC interfaces through HTTP, it is required to specify which RPCOps interface should be used.
A sibling of net.corda.internal.base.stream.DurableStreamContext but for HTTP RPC Client module
Once Artemis RPC elimination is complete those two classes might be merged into one, destination module TBD.
Represents a logical connection to the HTTP RPC server which may go up and down.
The proxy object can be used to make remote calls using the interface methods.
Can be attached to HttpRpcClient to be informed about connection and disconnection events.
HttpRpcConnectionListenerDistributor is responsible for distributing connection and disconnection events to interested listeners (HttpRpcConnectionListener).
Simple implementation of PositionManager that holds net.corda.v5.base.stream.DurableCursor position in memory.
RemoteClient implementations are responsible for making remote calls to the server and returning the response,
after potentially deserializing.
Analog of Apache HTTP's HttpContext can be extended to support storing state for challenge response based schemes
(extensions in package net.corda.v5.httprpc.client.internal.processing)