com.r3corda.protocols / TwoPartyDealProtocol / FixingRoleDecider

FixingRoleDecider

class FixingRoleDecider : ProtocolLogic<Unit>

This protocol looks at the deal and decides whether to be the Fixer or Floater role in agreeing a fixing.

It is kicked off as an activity on both participant nodes by the scheduler when its time for a fixing. If the Fixer role is chosen, then that will be initiated by the FixingSessionInitiation message sent from the other party and handled by the FixingSessionInitiationHandler.

TODO: Replace FixingSessionInitiation and FixingSessionInitiationHandler with generic session initiation logic once it exists.





Types

LOADING class LOADING : Step

Constructors

<init> FixingRoleDecider(ref: StateRef, timeout: Duration, progressTracker: ProgressTracker = tracker())

This protocol looks at the deal and decides whether to be the Fixer or Floater role in agreeing a fixing.

Properties

progressTracker val progressTracker: ProgressTracker

Override this to provide a ProgressTracker. If one is provided and stepped, the framework will do something helpful with the progress reports. If this protocol is invoked as a sub-protocol of another, then the tracker will be made a child of the current step in the parent. If its null, this protocol doesnt track progress.

ref val ref: StateRef
timeout val timeout: Duration
topic val topic: String

The topic to use when communicating with other parties. If more than one topic is required then use sub-protocols. Note that this is temporary until protocol sessions are properly implemented.

Inherited Properties

logger val logger: <ERROR CLASS>

This is where you should log things to.

psm lateinit var psm: ProtocolStateMachine<*>

Reference to the Fiber instance that is the top level controller for the entire flow.

serviceHub val serviceHub: ServiceHub

Provides access to big, heavy classes that may be reconstructed from time to time, e.g. across restarts. It is only available once the protocol has started, which means it cannnot be accessed in the constructor. Either access this lazily or from inside call.

Functions

call fun call(): Unit

This is where you fill out your business logic.

Inherited Functions

receive fun <T : Any> receive(otherParty: Party): UntrustworthyData<T>
fun <T : Any> receive(otherParty: Party, receiveType: Class<T>): UntrustworthyData<T>
registerSession fun registerSession(receivedHandshake: HandshakeMessage): Unit

If a node receives a HandshakeMessage it needs to call this method on the initiated receipt protocol to enable communication between it and the sender protocol. Calling this method, and other initiation steps, are already handled by AbstractNodeService.addProtocolHandler.

send fun send(otherParty: Party, payload: Any): Unit
sendAndReceive fun <T : Any> sendAndReceive(otherParty: Party, payload: Any): UntrustworthyData<T>
fun <T : Any> sendAndReceive(otherParty: Party, payload: Any, receiveType: Class<T>): UntrustworthyData<T>
subProtocol fun <R> subProtocol(subLogic: ProtocolLogic<R>, inheritParentSessions: Boolean = false): R

Invokes the given subprotocol by simply passing through this ProtocolLogics reference to the ProtocolStateMachine and then calling the call method.

Companion Object Functions

tracker fun tracker(): ProgressTracker