[Image](/uploads/documents/8/c/2/f/8c2fd06048f22f2c26c8dd372dcf93bf/p28_1.jpg) ## ? Session type ## Session? • Interaction of two or more entities. • It has a beginning and (usually) an end. • In between, a sequence interactions is happening. ## Session? • Can we describe a valid sequence of interactions? • Interaction diagram Branching ![Image](/uploads/documents/8/c/2/f/8c2fd06048f22f2c26c8dd372dcf93bf/p31_1

Initialization :read config file; :init internal variable; end group group Running group :wait for user interaction; :print information; end group stop @enduml ![Image](/uploads/documents/e/0/1/d/e01df2dbb3d71 { :read config file; :init internal variable; } partition Running { :wait for user interaction; :print information; } stop @enduml ![Image](/uploads/documents/e/0/1/d/e01df2dbb3d71e7189 { :read config file; :init internal variable; } partition Running { :wait for user interaction; :print information; } stop @enduml ![Image](/uploads/documents/e/0/1/d/e01df2dbb3d71e718

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between appli- cations, peers and orderers. Let’s investigate this in a little more detail. 60 in their organization, or peers in another organization, depending on the nature of the ledger interaction that’s required. For ledger-query interactions, applications typically connect to their own orga- distributed, replicated ledger. Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between applications, peers and orderers. Let’s investigate this in a little more detail. ![Im in their organization, or peers in another organization, depending on the nature of the ledger interaction that's required. For ledger-query interactions, applications typically connect to their own distributed, replicated ledger. ## Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between applications, peers and orderers. Let’s investigate this in a little more detail. ![Im in their organization, or peers in another organization, depending on the nature of the ledger interaction that's required. For ledger-query interactions, applications typically connect to their own distributed, replicated ledger. ## Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

communication over TCP, WebSocket, and other byte stream transports, using one of the following interaction models: • Request-Response — send one message and receive one back. • Request-Stream—send one higher level, independent concern. The main contract io.rsocket.RSocket models the four request interaction types with Mono representing a promise for a single message, Flux a stream of messages, and io request message. ② Provide data for the request message. ③ Declare the expected response. The interaction type is determined implicitly from the cardinality of the input and output. The above example is

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between applications, peers and orderers. Let’s investigate this in a little more detail. ![I in their organization, or peers in another organization, depending on the nature of the ledger interaction that's required. For ledger-query interactions, applications typically connect to their own distributed, replicated ledger. ## Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between applications, peers and orderers. Let’s investigate this in a little more detail. ![Im in their organization, or peers in another organization, depending on the nature of the ledger interaction that's required. For ledger-query interactions, applications typically connect to their own distributed, replicated ledger. ## Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between appli- cations, peers and orderers. Let’s investigate this in a little more detail. 4.7 in their organization, or peers in another organization, depending on the nature of the ledger interaction that’s required. For ledger-query interactions, applications typically connect to their own orga- distributed, replicated ledger. Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned

ledger query transaction is returned immediately, whereas ledger updates involve a more complex interaction between appli- cations, peers and orderers. Let’s investigate this in a little more detail. Peers in their organization, or peers in another organization, depending on the nature of the ledger interaction that’s required. For ledger-query interactions, applications typically connect to their own orga- distributed, replicated ledger. Phase 1: Proposal Phase 1 of the transaction workflow involves an interaction between an application and a set of peers — it does not involve orderers. Phase 1 is only concerned