-
Notifications
You must be signed in to change notification settings - Fork 88
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
New start strategy for miniprotocols #5048
Conversation
Fixes #5037 |
f7bf7c8
to
1d3b911
Compare
6ec7cda
to
d0a5ebc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, only one nomenclature comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks Karl; a few remarks.
cb4b76d
to
aa7bc10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
781e774
to
8b3ed1e
Compare
Add a new start strategy for miniprotocols. StartOnDemandAny will start the miniprotocol as soon as any other StartOnDemand protocols start. StartOnDemandAny is used by the responder side for KeepAlive to ensure that it is always active when any other protocol is running.
Adapt test cases so that the StartOnDemandAny strategy is tested too.
TraceStartOnDemand should be used when we intend to start a miniprotocol on demand. TraceStartedOnDemand should be used once the miniprotocol has started.
8b3ed1e
to
06beeb2
Compare
Description
Add a new start strategy for miniprotocols. StartOnDemandAny will start the miniprotocol as soon as any other StartOnDemand protocols start.
StartOnDemandAny is used by the responder side for KeepAlive to ensure that it is always active when any other protocol is running.
Checklist
Quality
Maintenance
ouroboros-network
project.