-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORE-15757 flow session refactor #1208
CORE-15757 flow session refactor #1208
Conversation
Non-blocking downstream job failed for corda-e2e-test https://ci02.dev.r3.com/job/Corda5/job/corda-api-compatibility/job/PR-1208/13/ has failed for PR 1208 build 13 Please investigate if your changes may have broken compilation on https://github.com/corda/corda-e2e-tests |
Jenkins build for PR 1208 build 19 Build Successful: |
application/src/main/java/net/corda/v5/application/messaging/FlowMessaging.java
Outdated
Show resolved
Hide resolved
application/src/main/java/net/corda/v5/application/messaging/FlowMessaging.java
Outdated
Show resolved
Hide resolved
…low info and flows which start with a receive
@chrisr3 as mentioned in the draft text this PR is not for review yet |
This change looks like something unexpected that is difficult just to ignore... |
I may have made some updates this morning.... completely unrelated to your comments.... 👀 |
…E-15757/flow-session-refactor
…E-15757/flow-session-refactor # Conflicts: # gradle.properties
…topic (#1213) change topic permissions
…E-15757/flow-session-refactor # Conflicts: # gradle.properties
…E-15757/flow-session-refactor # Conflicts: # gradle.properties
…t so it can be set both directions (#1212) Remove config fields not used anymore. counterparty lookups are no longer retriable. Session events are not resent.
…E-15757/flow-session-refactor # Conflicts: # gradle.properties
Flow Session Refactor to reduce the total messages exchanged between session counterparties.
SessionInit info can now be piggybacked onto SessionData messages.
SessionAcks are removed.
SessionContextProperties are piggybacked onto any SessionEvents as SessionConfirm is not always sent.
Add new initiateFlow API to allow the initiator to define whether a SessionClose message should be sent by the initiated party when their flow finishes or when they call close. Whichever comes first.
Runtime-OS:
corda/corda-runtime-os#4446
E2E Tests
https://github.com/corda/corda-e2e-tests/pull/218